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

Previous Next

Full log

Message #17 received at 31315 <at> debbugs.gnu.org (full text, mbox):

From: Andreas Schwab <schwab <at> linux-m68k.org>
To: Eli Zaretskii <eliz <at> gnu.org>
Cc: handa <at> gnu.org, 31315 <at> debbugs.gnu.org, wl <at> gnu.org
Subject: Re: bug#31315: wrong font encoding for fallback font
Date: Mon, 30 Apr 2018 22:03:42 +0200

On Apr 30 2018, Eli Zaretskii <eliz <at> gnu.org> wrote:

>> From: Andreas Schwab <schwab <at> linux-m68k.org>
>> Cc: Werner LEMBERG <wl <at> gnu.org>,  Kenichi Handa <handa <at> gnu.org>,  31315 <at> debbugs.gnu.org
>> Date: Mon, 30 Apr 2018 17:42:50 +0200
>> 
>> On Apr 30 2018, Eli Zaretskii <eliz <at> gnu.org> wrote:
>> 
>> > 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.
>
> Well, if we want to limit the repertory, then why not
> gb18030-4-byte-bmp, which AFAIU is the mandatory part of gb18030?

All gb18030 encoded fonts I found only provide 2-byte codes.  That may
be an inherent limitation.

Andreas.

-- 
Andreas Schwab, schwab <at> linux-m68k.org
GPG Key fingerprint = 7578 EB47 D4E5 4D69 2510  2552 DF73 E780 A9DA AEC1
"And now for something completely different."

Previous Next

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