Bug#742767: TeX Gyre OpenType and wrongly(?) named glyphs
On 7/7/2014 10:08 AM, Fabian Greffrath wrote:
Isn't Times one of the fonts that are by definition of the PDF standard
explicitely not required to get embedded?
Those 7+bit times of a default minimal set of 15 fonts (these were
embedded in printers which at some point made sense due to bandwidth et
etc) are behind us. Of course most printers will still have these fonts
because they are part of old standards. Not embedding a font has no
benefits and for archival pdf (a/x) fonts have to be embedded. (Nowadays
a mediocre picture taken by some gadget takes more space than a font in
a document.) In fact, if I get a pdf file with no fonts embedded and it
doesn't show up ok, I'd not even bother figuring out why and simple
discard the pdf.
Now, adding ff as well as f_f to a font mapping to the same glyph might
work ok for applications that look for ff but it might as well confuse
applications that like to see f_f (think of a one-to-one mapping: which
one wins ff <-> some slot or f_f <-> slot ?). So, i guess some testing
is needed as fixing one and breaking another set of applications doesn't
help. So, all applications that want to support the old stuff and new
stuff need to support (ff, f_f) <=> slot mapping.
Hans
-----------------------------------------------------------------
Hans Hagen | PRAGMA ADE
Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
tel: 038 477 53 69 | voip: 087 875 68 74 | www.pragma-ade.com
| www.pragma-pod.nl
-----------------------------------------------------------------
Reply to: