[Bug 458476] RFE: Support OpenType CFF fonts

[bugzilla at redhat.com]

Please do not reply directly to this email. All additional
comments should be made in the comments box of this bug.


https://bugzilla.redhat.com/show_bug.cgi?id=458476





--- Comment #9 from Vasile Gaburici <gaburici at cs.umd.edu>  2008-08-09 14:06:49 EDT ---
(In reply to comment #8)
> (In reply to comment #5)
> > Created an attachment (id=313875)
 --> (https://bugzilla.redhat.com/attachment.cgi?id=313875) [details] [details]
> > upstreams version, targeted for 3.2
> > 
> > so upstream already has that much for layout the font displaying it, what's
> > missing is the printing and pdf export portion apparently
> 
> A problem solved a couple of year back in XeTeX. The solution is not ideal, but
> works ok in practice: CFF fonts get converted on the fly to CID-keyed Type 1
> fonts (/CIDFontType0); the embedding does not use a /FontFile3 Subtype key,
> which is the direct way to embed a CFF font in a PDF.

Correction: XeTeX does embed CFF fonts without conversion. I was confused
because the /Subtype key comes after the (long) /CIDSet business, and it uses
/Subtype/CIDFontType0C for /FontFile3, not /Subtype/OpenType. The reason why
XeTeX uses /CIDFontType0C is that the /OpenType subtype requires PDF-1.6, while
/CIDFontType0C works in PDF-1.3, which is what XeTeX (xdvipdfmx actually)
outupts.

To further add to the confusion, evince displays CFF fonts embedded with
/CIDFontType0C as "Type 1C (CID)" in the font info box, while pdffonts lists
them as "CID Type 0C".

-- 
Configure bugmail: https://bugzilla.redhat.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.