From: Andrey Repin <anrdaemon@yandex.ru>
To: Sebastien Vauban <sva-news@mygooglest.com>, cygwin@cygwin.com
Subject: Re: Font support of UTF-8 chars differ between w32 Emacs and Cygwin Emacs
Date: Thu, 11 Sep 2014 13:05:00 -0000 [thread overview]
Message-ID: <1983918876.20140911163043@yandex.ru> (raw)
In-Reply-To: <867g1atq2j.fsf@somewhere.org>
Greetings, Sebastien Vauban!
>>> The problem would be with Cygwin in general, then, if not limited to
>>> Emacs.
>>>
>>> But why the same fonts (Consolas, Lucida Console) don't display the same
>>> range of characters in both worlds?
>>
>> You seem to assume that those fonts define that particular glyph.
> Yes, I was.
>> Both fonts you use as an example exist in multiple versions with
>> differing UTF-8 support. If they don't have that glyph (which is
>> likely, given the results you report), then Emacs would try to get it
>> from another font with the same dimensions (I don't know if mintty
>> does font substitution and if so, how) and the results very much
>> depend on the font maps used.
> I didn't know about that mechanism. But, then, the question is: why does
> Windows Emacs find a substitution, and not Cygwin Emacs (for the same
> font)?
Because of different substitution mechanics.
--
WBR,
Andrey Repin (anrdaemon@yandex.ru) 11.09.2014, <16:30>
Sorry for my terrible english...
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
next prev parent reply other threads:[~2014-09-11 12:35 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-03 12:43 Sebastien Vauban
2014-09-03 14:00 ` Ken Brown
2014-09-03 15:04 ` Sebastien Vauban
2014-09-10 19:25 ` Ken Brown
2014-09-11 9:19 ` Sebastien Vauban
2014-09-11 10:23 ` Achim Gratz
2014-09-11 11:27 ` Sebastien Vauban
2014-09-11 13:05 ` Andrey Repin [this message]
2014-09-11 21:12 ` Ken Brown
2014-09-11 9:27 ` Marco Atzeri
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=1983918876.20140911163043@yandex.ru \
--to=anrdaemon@yandex.ru \
--cc=cygwin@cygwin.com \
--cc=sva-news@mygooglest.com \
/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.
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).