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

From: Andreas Schwab <[email-masked]>
Date: Mon, 30 Apr 2018 17:42:50 +0200

On Apr 30 2018, Eli Zaretskii <[email-masked]> wrote:

> If you look in xfont_encode_char, you will see that it does encode the
> character before handing it to the font-drawing function.  But I see
> that font-encoding-alist has this to say about gb18030:
>
>  ("gb18030" unicode)
>
> Does replacing that with something like this:
>
>  ("gb18030" (gb18030 . unicode))
>
> solve the problem?

I think it should be gb18030-2-byte, both as encoding and repertory.

Andreas.

-- 
Andreas Schwab, [email-masked]
GPG Key fingerprint = 7578 EB47 D4E5 4D69 2510  2552 DF73 E780 A9DA AEC1
"And now for something completely different."