From: Werner LEMBERG <wl@gnu.org>
To: eliz@gnu.org
Cc: 31315@debbugs.gnu.org
Subject: bug#31315: wrong font encoding for fallback font
Date: Wed, 02 May 2018 09:27:43 +0200 (CEST) [thread overview]
Message-ID: <20180502.092743.668654792279683778.wl@gnu.org> (raw)
In-Reply-To: <20180501.213014.1436609899151985328.wl@gnu.org>
> To a certain extent it is valid to assume that a user of GB18030
> expects Chinese glyph representation forms for characters in the CJK
> range. However, since full Unicode is supported, this assumption is
> rather weak.
>
> The X11 interface is too old actually to handle GB18030 correctly.
Oops, please ignore this sentence, which I forgot to delete.
> For example, on my GNU/Linux box xft offers the following:
>
> -adobe-noto sans cjk jp thin-light-r-normal--0-0-0-0-p-0-gb18030.2000-0
>
> As the `jp' in the name indicates this font contains Japanese glyph
> representation forms. Since `Noto Sans CJK' provides all CJK glyphs
> in the BMP, xft happily tags it with GB18030...
Werner
next prev parent reply other threads:[~2018-05-02 7:27 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
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 [this message]
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=20180502.092743.668654792279683778.wl@gnu.org \
--to=wl@gnu.org \
--cc=31315@debbugs.gnu.org \
--cc=eliz@gnu.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.