Re: Choice of fonts displaying etc/HELLO

[Jason Rumney]

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.