unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
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: Thu, 03 May 2018 21:05:28 +0200 (CEST)	[thread overview]
Message-ID: <20180503.210528.278141526929157986.wl@gnu.org> (raw)
In-Reply-To: <83a7tgpr43.fsf@gnu.org>


>> I can only repeat that Emacs might tag a certain text with GB18030
>> so that the user can deduce a Chinese origin.  However, there is
>> *no* guarantee that the user gets a Chinese-flavoured font – at
>> least not from the xft interface.[**]
> 
> IME, there's no guarantee about anything in the Emacs font look up
> heuristics, except that empirically it does TRT in about 85% of
> uses.

If you don't install pan-CJK Unicode fonts, I fully agree :-)

> May I invite you to work on revisiting the design and implementation
> of the Emacs font-look up facilities, and on modernizing them?  I'm
> afraid we didn't have an active developer in this area for several
> years, and I fear that we will stagnate (or already are stagnating).

Alas, my Elisp knowledge is ... well ... not impressive.  Basically,
I'm just an Emacs user, not an Emacs developer.

With Xft, there is no possibility for improvement IMHO.  The probably
best choice is to switch to Pango for font access (in case you don't
do that already).  An Emacs charset essentially triggers a language
and script setting, and those two parameters can be passed to Pango,
AFAIK.


    Werner

  reply	other threads:[~2018-05-03 19:05 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
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 [this message]
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

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20180503.210528.278141526929157986.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 public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).