Apache OpenOffice (AOO) Bugzilla – Issue 79187
Aqua: Type1 fonts not yet supported in PDF Export
Last modified: 2017-05-20 11:31:09 UTC
Tested: aquavc|01_20070630 PPC G4 writer document created a file using OpenType font, TrueType font and Postscript font. exported to pdf and resulting file only contained TrueType font OpenType and Postscript font were boxes, spaces, and apple icons in each line (file sent to printer and fonts printed correctly)
- Truetype fonts are already supported - OpenType fonts with truetype glyphs are already supported - OpenType fonts with CFF glyphs will be supported (issue 43029) - Type1 fonts have been obsoleted by OpenType fonts more than five years ago - Bitmap fonts have been obsoleted by scalable font technologies and they'll probably never be support them for PDF export So, what is remaining are Type1 fonts. Since they are not available on fresh OSX installations, I'm wondering if there really is much interest in having them supported? Please vote for this issue if your PDF export use cases would benefit from Type1 support. In case some use cases for PDF export would benefit from support for bitmap fonts I suggest to open a new issue and collect votes there.
accepted
this is another "type1 subsetting needed" issue
Despite the presence of OpenType, there are still a hell of a lot of Type1 fonts out there in daily use, a huge investment by a lot of people. One doesn't throw away a multi-thousand dollar investment just because Adobe declares OpenType to have "obsoleted" Type1. Can this please be fixed? I used my two votes for this issue.
On a related note, It looks like there is an off-by-one error when exporting postcript fonts to pdf In file vcl/source/gdi/pdfwriter_impl.cxx line 3390 Substract a 1 from the right hand side.
(In reply to comment #5) > On a related note, > > It looks like there is an off-by-one error when exporting postcript fonts to > pdf > > In file vcl/source/gdi/pdfwriter_impl.cxx > I should've been clearer, the problem is in PDFWriterImpl::emitEmbeddedFont When assigning the value of nLength3 (line 3390), nIndex should now point *before* the first of the 512 '0' characters marking the fixed content portion. > Substract a 1 from the right hand side.
Created attachment 80228 [details] fix calculation of "remaining bytes in a PFB file" You are right, thanks for the idea! The block above the one you mentioned shows that nIndex already starts with one less; so if the number of remaining bytes is calculated this has to be taken into account. Please review the patch.
Comment on attachment 80228 [details] fix calculation of "remaining bytes in a PFB file" Looks good, indeed!
Reset assigne to the default "issues@openoffice.apache.org".