From: Ilya Zakharevich <ilya@math.berkeley.edu>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 19993@debbugs.gnu.org
Subject: bug#19993: 25.0.50; Unicode fonts defective on Windows
Date: Sun, 8 Mar 2015 00:46:07 -0800 [thread overview]
Message-ID: <20150308084607.GA2135@math.berkeley.edu> (raw)
In-Reply-To: <20150308083805.GA1763@math.berkeley.edu>
On Sun, Mar 08, 2015 at 12:38:05AM -0800, Ilya Zakharevich wrote:
> When Emacs wants to show a character using a fontset:
> • Emacs looks in the fontset and finds the font specifications associated
> to this character.
> • Emacs checks which Unicode Subset contains the given character.
> (What if not unique???)
> • From fonts matching the font specifications, Emacs picks up those
> which have this Unicode Subset “identified” within the font.
> • From these, Emacs choses one (which?).
>
> Emacs uses this procedure for two fontsets: the currently enabled one, and
> the default fontset. If none of two obtained fonts supports the given
> character, a HEX representation is shown.
> =======================================================
Interesting tidbit:
57 D800 - DFFF Non-Plane 0. Note that setting this bit implies that
there is at least one supplementary code point
beyond the Basic Multilingual Plane (BMP) that
is supported by this font. See Surrogates and
Supplementary Characters.
Extrapolating (since there is no other way to treat this), having a
Subset “identified” may mean just that there is at least 1 character
in this range supported by the font. ;-) :-(
Ilya
next prev parent reply other threads:[~2015-03-08 8:46 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-03 22:02 bug#19993: 25.0.50; Unicode fonts defective on Windows Ilya Zakharevich
2015-03-04 17:59 ` Eli Zaretskii
2015-03-05 21:49 ` Ilya Zakharevich
2015-03-05 22:05 ` Ilya Zakharevich
2015-03-06 10:45 ` Eli Zaretskii
2015-03-06 11:38 ` Ilya Zakharevich
2015-03-06 14:00 ` Eli Zaretskii
2015-03-06 16:21 ` Ilya Zakharevich
2015-03-06 20:11 ` Eli Zaretskii
2015-03-06 21:12 ` Eli Zaretskii
2015-03-06 22:13 ` Ilya Zakharevich
2015-03-07 8:18 ` Eli Zaretskii
2015-03-08 7:45 ` Ilya Zakharevich
2015-03-08 15:52 ` Eli Zaretskii
2015-03-08 8:38 ` Ilya Zakharevich
2015-03-08 8:46 ` Ilya Zakharevich [this message]
2015-03-10 16:29 ` Ilya Zakharevich
2015-03-10 17:05 ` Eli Zaretskii
2015-03-10 17:41 ` Eli Zaretskii
2015-03-10 20:32 ` Ilya Zakharevich
2015-03-11 4:28 ` Eli Zaretskii
2015-03-11 19:49 ` Ilya Zakharevich
2015-03-11 20:21 ` Eli Zaretskii
2015-03-12 18:16 ` Eli Zaretskii
2015-03-13 1:52 ` Ilya Zakharevich
2015-03-13 7:34 ` Eli Zaretskii
2015-03-13 4:50 ` Ilya Zakharevich
2015-03-13 6:16 ` Eli Zaretskii
2015-03-08 15:55 ` Eli Zaretskii
2015-03-06 22:08 ` Ilya Zakharevich
2015-03-07 8:14 ` Eli Zaretskii
2015-03-08 7:41 ` Ilya Zakharevich
2015-03-08 15:51 ` Eli Zaretskii
2015-03-08 16:20 ` Ilya Zakharevich
2015-03-08 17:01 ` 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=20150308084607.GA2135@math.berkeley.edu \
--to=ilya@math.berkeley.edu \
--cc=19993@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).