logo       

Re: Re(8): Italic open-o in omega: msg#00025

tex.omega.user

Subject: Re: Re(8): Italic open-o in omega

> >i think that it is not a good approach to translate TrueType/OpenType
> >fonts to Type1 (even on the fly), since it will reduce the quality of
> >TrueType fonts.
>
> if you mean hinting, then (a) ttf2pt1 does autohinting, (b) for high
> resolutions we don't need it in the first place, (c) it would be even
> more interesting to convert TrueType hints into type 1 ones, or something
> equivalent, instead of blindly relying on the TrueType interpreter

Trying to convert Truetype instructions to Type 1 hints would be *very*
interesting indeed; or rather, it would be extremely tricky to get right. Note
that conversion of outlines to Type 1 will yield (admittedly very small)
rounding errors. Also, relying on the TrueType interpreter seems to be quite
correct if the user has picked this TrueType font. All in all, I don't think
converting TrueType to Type1 would be right if one can help it.

> > YH> Imagine that in OpenType fonts you can put italic, roman and
> > YH> small-caps into the same font and distinguish them by
> > YH> "properties". This means that you can have kerning between all of
> > YH> them... no need for the \/ macro anymore since we stay in the
> > YH> same font when we write "\emph{and})"... And these OpenType
> > YH> Computer Modern fonts will be useable by other software as well,
> > YH> such as InDesign
> >
> >sounds promising, but in my opinion, all Omega-specific font metric is
> >better kept in separate files... that will give more flexibility:
>
> and more chaos! SFNT files are designed in such a way that you can
> store many kinds of information in various tables, that's better than
> having different files and loose track of them, mix up different versions,
> etc. etc.

Also, I would consider the possibility that even commercial fonts will contain
the extra information, once the OpenType specs do specify them (because that's
supposedly why OpenType has "Open" in its name).

Regards,
Rogier


--
Dit bericht is gescand op virussen en andere gevaarlijke inhoud door ULCN
MailScanner en het bericht lijkt schoon te zijn.
This message has been scanned for viruses and dangerous content by ULCN
MailScanner, and is believed to be clean.


<Prev in Thread] Current Thread [Next in Thread>
Google Custom Search

News | FAQ | advertise