Subject: bug#31315: wrong font encoding for fallback font

From: Eli Zaretskii <[email-masked]>
Date: Tue, 01 May 2018 18:00:42 +0300

> Date: Tue, 01 May 2018 11:11:30 +0200 (CEST)
> Cc: [email-masked], [email-masked], [email-masked]
> From: Werner LEMBERG <[email-masked]>
> 
> 
> >> 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.