This is the mail archive of the cygwin mailing list for the Cygwin project.

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: Font support of UTF-8 chars differ between w32 Emacs and Cygwin Emacs

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.

Andrey Repin ( 11.09.2014, <16:30>

Sorry for my terrible english...

Problem reports:
Unsubscribe info:

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]