[Fontinst] Re: Bug in fontinstversion{1.927}

Peter Dyballa Peter_Dyballa at Web.DE
Fri Jan 28 00:48:01 CET 2005

Am 27.01.2005 um 14:59 schrieb Lars Hellström:

> I've checked the properties now: The tie accent (and its variants) is
> definitely U+0361 rather than U+2040. The former has character class Mn
> (nonspacing mark) like all the other accents, whereas the latter has
> character class Pc (connecting punctuation) and is thus most like
> underscore (U+005F, LOW LINE). A U+0361 should be placed above a pair 
> of
> letters, whereas a U+2040 would rather be placed between them.

Actually it seems that the tie accent does not get used in text:

-------------- next part --------------
Skipped content of type multipart/appledouble-------------- next part --------------

This is Lucida Sans. nfssfont.tex reveals that all four tie accents are 
known. They come from U+2040 because 'dead key' U+0361 is not defined 
in the TrueType font.

On the other hand I really wonder why \emph{} or \textit{} use the 
wrong ligatures ...



How many Microsoft engineers does it take to screw in a lightbulb?
They just redefine "dark" as the new standard.

More information about the fontinst mailing list