From: Jason Rumney <jasonr@gnu.org>
To: Juanma Barranquero <lekktu@gmail.com>
Cc: emacs- devel <emacs-devel@gnu.org>
Subject: Re: Choice of fonts displaying etc/HELLO
Date: Wed, 30 Jul 2008 16:03:44 +0100 [thread overview]
Message-ID: <489082D0.9040706@gnu.org> (raw)
In-Reply-To: <48907856.6040308@gnu.org>
Jason Rumney wrote:
> Juanma Barranquero wrote:
>
>> In etc/HELLO there are two instances of U+2200 (FOR ALL). The newest
>> release of DejaVu (2.26) added a glyph for that codepoint to DejaVu
>> Sans Mono, which I use as default font.
>>
>> Now the weird thing is, the first FOR ALL in etc/HELLO is shown as
>>
>> character: ∀ (8704, #o21000, #x2200)
>> preferred charset: unicode (Unicode (ISO10646))
>> code point: 0x2200
>> syntax: . which means: punctuation
>> category: h:Korean j:Japanese
>> buffer code: #xE2 #x88 #x80
>> file code: ESC #x24 #x42 #x22 #x4F (encoded by coding system
>> iso-2022-7bit-dos)
>> display: by this font (glyph code)
>> uniscribe:-outline-DejaVu Sans
>> Mono-normal-normal-normal-mono-13-*-*-*-c-*-iso10646-1 (#x7A2)
>>
>> while the second one is
>>
>> character: ∀ (8704, #o21000, #x2200)
>> preferred charset: unicode (Unicode (ISO10646))
>> code point: 0x2200
>> syntax: . which means: punctuation
>> category: h:Korean j:Japanese
>> buffer code: #xE2 #x88 #x80
>> file code: ESC #x24 #x42 #x22 #x4F (encoded by coding system
>> iso-2022-7bit-dos)
>> display: by this font (glyph code)
>> uniscribe:-outline-MS
>> Mincho-normal-normal-normal-mono-13-*-*-*-c-*-jisx0208*-* (#x421)
>>
>> Shouldn't it use DejaVu Sans Mono for both?
>
> I have no idea why these use different fonts (even the file code is the
> same, so it is not a difference in iso-2022 codepoints chosen), on my
> installation both use MS Mincho (I probably have an older version of
> DejaVu Mono that does not support that character). And why does that
> character have a category of h:Korean j:Japanese?
This is strange. After upgrading my DejaVu fonts to the latest version,
both for-all signs are displayed using DejaVu Sans Mono. But I do now
notice that the first has:
There are text properties here:
auto-composed t
charset mule-unicode-0100-24ff
while the second says:
auto-composed t
charset japanese-jisx0208
So probably the file code is different despite what file code is
reported above that.
next prev parent reply other threads:[~2008-07-30 15:03 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-29 20:49 segmentation fault displaying etc/HELLO on Windows Juanma Barranquero
2008-07-30 6:48 ` Jason Rumney
2008-07-30 11:48 ` Juanma Barranquero
2008-07-30 13:05 ` Jason Rumney
2008-07-30 13:11 ` Jason Rumney
2008-07-30 14:03 ` Juanma Barranquero
2008-07-30 14:19 ` Choice of fonts displaying etc/HELLO (was: Re: segmentation fault displaying etc/HELLO on Windows) Jason Rumney
2008-07-30 15:03 ` Jason Rumney [this message]
2008-07-30 15:26 ` Choice of fonts displaying etc/HELLO Juanma Barranquero
2008-08-01 12:50 ` Kenichi Handa
2008-08-01 12:56 ` Choice of fonts displaying etc/HELLO (was: Re: segmentation fault displaying etc/HELLO on Windows) Kenichi Handa
2008-08-01 13:17 ` Choice of fonts displaying etc/HELLO Jason Rumney
2008-08-01 13:51 ` Eli Zaretskii
2008-08-05 7:33 ` Kenichi Handa
2008-08-05 18:12 ` Eli Zaretskii
2008-08-06 5:30 ` Kenichi Handa
2008-08-06 6:14 ` Stephen J. Turnbull
2008-08-06 6:29 ` Kenichi Handa
2008-08-06 15:52 ` Stephen J. Turnbull
2008-08-06 17:56 ` Eli Zaretskii
2008-08-07 1:14 ` Kenichi Handa
2008-08-07 3:22 ` Eli Zaretskii
2008-08-07 3:54 ` Kenichi Handa
2008-08-07 4:54 ` Miles Bader
2008-08-07 18:03 ` Eli Zaretskii
2008-08-07 19:30 ` Stephen J. Turnbull
2008-08-11 8:48 ` Miles Bader
2008-08-11 19:03 ` Eli Zaretskii
2008-07-31 1:49 ` segmentation fault displaying etc/HELLO on Windows Kyle M. Lee
2008-07-31 2:03 ` Juanma Barranquero
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=489082D0.9040706@gnu.org \
--to=jasonr@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=lekktu@gmail.com \
/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).