This is the mail archive of the
mailing list for the Cygwin project.
Re: Font support of UTF-8 chars differ between w32 Emacs and Cygwin Emacs
- From: Sebastien Vauban <sva-news at mygooglest dot com>
- To: cygwin at cygwin dot com
- Date: Thu, 11 Sep 2014 12:21:56 +0200
- Subject: Re: Font support of UTF-8 chars differ between w32 Emacs and Cygwin Emacs
- Authentication-results: sourceware.org; auth=none
- References: <868um0dgfp dot fsf at somewhere dot org> <54108F3C dot 5010103 at cornell dot edu> <86a966bn5v dot fsf at somewhere dot org> <87bnqmy0b4 dot fsf at Rainer dot invalid>
Achim Gratz wrote:
> Sebastien Vauban writes:
>> The problem would be with Cygwin in general, then, if not limited to
>> 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
Problem reports: http://cygwin.com/problems.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple