[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#742767: TeX Gyre OpenType and wrongly(?) named glyphs




Fabian:
they are not installed by default, that is. But once they are installed,
they take precedence.

OK, we took a shortcut. :-)

Incidentally, Debian/Ubuntu distribution ofers either "tex-gyre" or
"fonts-texgyre" packages, the former containing fonts in the Type 1 format, the latter -- fonts in OpenType format. And a user, having chosen the latter package, is thus forced to use OpenType as replacement fonts,
while the formr package cannot be used for this purpose.

J&P:
What about using Type 1 fonts for "compatibility purposes"?

Fabian:
We have chosen to use the OpenType fonts for text rendering, because
they are generally considered to be better rendered on screen.

Maybe the reason behind "generally better rendering" is that the fonts
that render better are internally TrueType (B-spline) fonts, while
TeX Gyre fonts are actually CFF (i.e., practically the same as Type 1).
It seems that screen-hinted B-spline fonts are usually indeed better rendered. So, we woulnd't expect the difference in the case of
TeX Gyre/Latin Modern.

Hans:
The texgyre opentype fonts are not supposed to be drop ins
for those standard (15 or so) ps fonts.

Agreed, as we already wrote.

Hans:
I think even the type1 texgyre isn't by definition metric compatible.

Metric compatibility was one of the major targets of the TeX Gyre project.
Rare incompatibilities with respect to the original metric files are carefully documented in the relevant documentation.

Having thought the matter over and having looked into TG Linux packages, we would suggest to use, anyway, Type 1 TG as legacy fonts and to change appropriately the content of packages -- and maybe names? ;-)

Cheers -- Jacko & Piotr

--
BOP s. c.
ul. Bora-Komorowskiego 24, 80-377 Gdansk, Poland
tel./fax (+48 58) 553 46 59
bop@bop.com.pl, http://www.bop.com.pl


Reply to: