From: Eli Zaretskii <eliz@gnu.org>
To: Andreas Schwab <schwab@linux-m68k.org>
Cc: 31315@debbugs.gnu.org
Subject: bug#31315: wrong font encoding for fallback font
Date: Tue, 01 May 2018 05:37:02 +0300 [thread overview]
Message-ID: <83sh7cqey9.fsf@gnu.org> (raw)
In-Reply-To: <87fu3ctqap.fsf@linux-m68k.org> (message from Andreas Schwab on Mon, 30 Apr 2018 22:03:42 +0200)
> From: Andreas Schwab <schwab@linux-m68k.org>
> Cc: wl@gnu.org, handa@gnu.org, 31315@debbugs.gnu.org
> Date: Mon, 30 Apr 2018 22:03:42 +0200
>
> >> > 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.
Thanks.
Werner, can you try that, please?
next prev parent reply other threads:[~2018-05-01 2:37 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-30 7:21 bug#31315: wrong font encoding for fallback font Werner LEMBERG
2018-04-30 15:13 ` Eli Zaretskii
2018-04-30 15:42 ` Andreas Schwab
2018-04-30 19:26 ` Eli Zaretskii
2018-04-30 20:03 ` Andreas Schwab
2018-05-01 2:37 ` Eli Zaretskii [this message]
2018-05-01 6:47 ` Werner LEMBERG
2018-05-01 8:13 ` Andreas Schwab
2018-05-01 9:11 ` Werner LEMBERG
2018-05-01 15:00 ` Eli Zaretskii
2018-05-01 17:42 ` Andreas Schwab
2018-05-05 8:57 ` Eli Zaretskii
2018-05-01 6:36 ` Werner LEMBERG
2018-05-01 15:22 ` Eli Zaretskii
2018-05-01 19:30 ` Werner LEMBERG
2018-05-02 7:27 ` Werner LEMBERG
2018-05-02 15:22 ` Eli Zaretskii
2018-05-03 5:52 ` Werner LEMBERG
2018-05-03 17:48 ` Eli Zaretskii
2018-05-03 19:05 ` Werner LEMBERG
2018-05-03 19:59 ` Eli Zaretskii
2018-05-04 5:11 ` Werner LEMBERG
2018-05-04 13:05 ` Eli Zaretskii
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=83sh7cqey9.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=31315@debbugs.gnu.org \
--cc=schwab@linux-m68k.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.