From: Kenichi Handa <handa@ni.aist.go.jp>
To: Stephen Berman <Stephen.Berman@gmx.net>
Cc: emacs-devel@gnu.org
Subject: Re: 23.0.60; peculiar error: "invalid font property", (:weight . r)
Date: Wed, 26 Dec 2007 09:57:52 +0900 [thread overview]
Message-ID: <E1J7Kam-0000XW-0E@etlken.m17n.org> (raw)
In-Reply-To: <874pec3ss3.fsf@escher.local.home> (message from Stephen Berman on Fri, 21 Dec 2007 17:40:44 +0100)
In article <874pec3ss3.fsf@escher.local.home>, Stephen Berman <Stephen.Berman@gmx.net> writes:
> [2 Emacs fontsets <text/plain (7bit)>]
> ! ==========================================================================
> ! Emacs
> ! ==========================================================================
[...]
> Emacs*Fontset-5:\
> -*-fixed-medium-r-*--12-*-*-*-*-*-fontset-12,\
> latin-iso8859-1:-*-fixed-medium-r-*--12-*-iso8859-1,\
> latin-iso8859-2:-*-fixed-medium-r-*--12-*-iso8859-2,\
> latin-iso8859-3:-*-fixed-medium-r-*--12-*-iso8859-3,\
> latin-iso8859-4:-*-fixed-medium-r-*--12-*-iso8859-4,\
> cyrillic-iso8859-5:-*-fixed-medium-r-*--12-*-iso8859-5,\
> greek-iso8859-7:-*-fixed-medium-r-*--12-*-iso8859-7,\
> latin-iso8859-15:-*-fixed-medium-r-*--12-*-iso8859-15 \
> hebrew-iso8859-8:-*-fixed-medium-r-*--12-*-iso8859-8,\
> latin-iso8859-9:-*-fixed-medium-r-*--12-*-iso8859-9,\
> katakana-jisx0201:-*-fixed-medium-r-*--12-*-jisx0201.1976-0,\
> japanese-jisx0208:-*-fixed-medium-r-*--12-*-jisx0208*-0,\
> korean-ksc5601:-*-fixed-medium-r-*--12-*-ksc5601.1987-0
This entry has a bug. The specifications for
latin-iso8859-15 and hebrew-iso8859-8 are not separated by
",". Previously Emacs silently ignored such specifications,
but the new code doesn't.
By the way, as this error message:
peculiar error: "invalid font property", (:spacing . iso8859)
is too cryptic, I'll try to improve it.
---
Kenichi Handa
handa@ni.aist.go.jp
next prev parent reply other threads:[~2007-12-26 0:57 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-19 14:58 23.0.60; peculiar error: "invalid font property", (:weight . r) Stephen Berman
2007-12-19 15:24 ` Jason Rumney
2007-12-19 15:32 ` Stephen Berman
2007-12-20 0:58 ` Kenichi Handa
2007-12-20 0:54 ` Kenichi Handa
2007-12-20 10:29 ` Stephen Berman
2007-12-20 11:21 ` Andreas Schwab
2007-12-20 14:14 ` Stephen Berman
2007-12-21 0:47 ` Kenichi Handa
2007-12-21 16:40 ` Stephen Berman
2007-12-23 18:40 ` hcz
2007-12-26 0:57 ` Kenichi Handa [this message]
2008-01-03 20:18 ` Attn. Andreas Schwab (was Re: 23.0.60; peculiar error: "invalid font property", (:weight . r)) Stephen Berman
2008-01-03 22:07 ` Andreas Schwab
2008-01-03 23:03 ` Attn. Andreas Schwab Stephen Berman
2007-12-20 10:54 ` 23.0.60; peculiar error: "invalid font property", (:weight . r) KOBAYASHI Yasuhiro
2007-12-20 12:42 ` Kenichi Handa
2007-12-20 14:14 ` Stephen Berman
2007-12-21 16:27 ` KOBAYASHI Yasuhiro
2007-12-26 1:56 ` Kenichi Handa
2007-12-26 15:47 ` KOBAYASHI Yasuhiro
2008-01-17 5:16 ` KOBAYASHI Yasuhiro
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=E1J7Kam-0000XW-0E@etlken.m17n.org \
--to=handa@ni.aist.go.jp \
--cc=Stephen.Berman@gmx.net \
--cc=emacs-devel@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).