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: Tue, 10 Mar 2015 13:32:24 -0700 [thread overview]
Message-ID: <20150310203224.GA325@math.berkeley.edu> (raw)
In-Reply-To: <838uf4697w.fsf@gnu.org>
On Tue, Mar 10, 2015 at 07:41:39PM +0200, Eli Zaretskii wrote:
> > > Choosing the first font which has a subset of a character “identified”
> > > is not a reasonable thing to do.
> >
> > See my other messages: I'm not sure we actually do that. It's
> > possible that the subrange test is used only as a filter, after we
> > already identified the candidate fonts.
>
> In fact, it's almost certainly a filter: at least my reading of
> ww32font.c:font_matches_spec is that if the font spec specifies a
> script, then fonts that do NOT have the corresponding subrange bit set
> are rejected.
So back to the drawing board:
• on your system
• with Symbola installed
• with the default configuration
I presume that Math Alphabeticals are not shown (but ARE shown when
Symbola is EXPLICITLY marked as the default font for them).
WHY?
With my conjectures, the explanation would be that a certain other
font on the system has the Math Alphabeticals Subset “identified”, so
this font is chosen by Emacs — but in reality, this font does not
support the whole subset, so the needed glyphs are missing. (For
example, DejaVu has Monospaced range, and nothing else. [Well, the
glyphs in the Monospaced range are totally broken, but that is
irrelevant for the current discussion!])
Without my conjecture, what would be your explanation?
Ilya
next prev parent reply other threads:[~2015-03-10 20:32 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
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 [this message]
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=20150310203224.GA325@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).