From: Eli Zaretskii <eliz@gnu.org>
To: Chong Yidong <cyd@gnu.org>
Cc: 4895@debbugs.gnu.org, cmr.pent@gmail.com, handa@m17n.org
Subject: bug#4895: 23.1; Incorrect font selected
Date: Mon, 09 Jul 2012 19:41:20 +0300 [thread overview]
Message-ID: <83d344lwen.fsf@gnu.org> (raw)
In-Reply-To: <87wr2d33og.fsf@gnu.org>
> From: Chong Yidong <cyd@gnu.org>
> Date: Mon, 09 Jul 2012 13:26:55 +0800
> Cc: 4895@debbugs.gnu.org, cmr.pent@gmail.com, Kenichi Handa <handa@m17n.org>
>
> Also, where in the code does this
>
> >> when you read a file with cp1251, the charset property
> >> `cp1251' is put on the buffer text. Thus the font-selector
> >> prefers a font whose registry is "microsoft-cp1251".
>
> occur?
decode_coding calls produce_annotation that calls produce_charset,
which puts the 'charset' text property on the decoded text.
Then font_for_char uses this property to get the charset ID with which
it calls fontset_font, which in turn calls fontset_find_font, which
prefers fonts whose repertory matches that ID.
> I took a quick look at the documentation, e.g. the docstring of
> new-fontset, and couldn't find the explanation of how the
> font-selector chooses the font to use from the list of font
> specifications. If the list of font specifications is not given in
> order of priority, that should be clearly explained somewhere.
The documentation of fontset stuff could use a lot of improvement.
prev parent reply other threads:[~2012-07-09 16:41 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-09 19:19 bug#4895: 23.1; Incorrect font selected Andrey Paramonov
2009-11-10 1:32 ` Kenichi Handa
2009-11-10 6:15 ` Андрей Парамонов
2009-11-10 8:10 ` Kenichi Handa
2009-11-11 10:45 ` Juri Linkov
2012-07-09 5:26 ` Chong Yidong
2012-07-09 8:10 ` Juri Linkov
2012-07-09 16:41 ` Eli Zaretskii [this message]
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=83d344lwen.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=4895@debbugs.gnu.org \
--cc=cmr.pent@gmail.com \
--cc=cyd@gnu.org \
--cc=handa@m17n.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.