GNU bug report logs - #31315
wrong font encoding for fallback font

Previous Next

Full log

View this message in rfc822 format

From: Eli Zaretskii <eliz <at> gnu.org>
To: Werner LEMBERG <wl <at> gnu.org>
Cc: handa <at> gnu.org, 31315 <at> debbugs.gnu.org, schwab <at> linux-m68k.org
Subject: bug#31315: wrong font encoding for fallback font
Date: Tue, 01 May 2018 18:00:42 +0300

> Date: Tue, 01 May 2018 11:11:30 +0200 (CEST)
> Cc: eliz <at> gnu.org, handa <at> gnu.org, 31315 <at> debbugs.gnu.org
> From: Werner LEMBERG <wl <at> gnu.org>
> 
> 
> >> You actually have found a font encoded in GB18030?  Which one?  I have
> >> never seen that.
> > 
> > The same that you have plus two others.
> 
> But those fonts are *not* encoded in GB18030 at all.  It is the X11
> font interface that provides GB18030 encoding access.
> 
> BTW, looking into my `/usr/share/fonts/encodings/large' directory, I
> see a file `gb18030.2000-0.enc.gz', which contains only two-byte
> entries.  In other words, it omits all three- and four-byte entries,
> thus covering only a subset of GB18030.

Andreas, given that '("gb18030" (gb18030 . unicode))' appears to work,
do you see any potential problems with using it, instead of
gb18030-2-byte?

Thanks.

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.