Bug Hunting Session
Bug 126242 - PDF-EXPORT: do not produce correct glyph outlines of OTF-CFF fonts subset to Type1 fonts, during subset some outline paths get shifted (at the end points, not the joins)
Summary: PDF-EXPORT: do not produce correct glyph outlines of OTF-CFF fonts subset t...
Status: NEW
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Printing and PDF export (show other bugs)
Version:
(earliest affected)
Inherited From OOo
Hardware: All All
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
: 99114 105979 (view as bug list)
Depends on:
Blocks: Font-Rendering PDF-Export
  Show dependency treegraph
 
Reported: 2019-07-05 11:14 UTC by medmedin2014
Modified: 2019-10-19 14:30 UTC (History)
10 users (show)

See Also:
Crash report or crash signature:


Attachments
OTF Wrong drawings in exported pdf (104.70 KB, application/x-xz)
2019-07-05 11:21 UTC, medmedin2014
Details
source odt + pdf output + version + fonts (230.58 KB, application/x-xz)
2019-07-06 11:44 UTC, medmedin2014
Details
Scribus sample (40.74 KB, application/pdf)
2019-07-06 11:59 UTC, medmedin2014
Details

Note You need to log in before you can comment on or make changes to this bug.
Description medmedin2014 2019-07-05 11:14:33 UTC
Description:
I tried to use EBGaramond otf fonts in writer, but when I export to pdf, some letters have error in shapes, I tried the same font with Scribus and Microsoft word but the exported pdf look perfect without errors.

Steps to Reproduce:
1- Open writer
2- Write some text with ebgramond font, and type some capital letters like N, M, T, F, Z
3- export to pdf
4- open pdf with some viewer and zoom letters to maximum

Actual Results:
some letters have wrong shapes and are corrupted

Expected Results:
All letters should look fine


Reproducible: Always


User Profile Reset: Yes



Additional Info:
Comment 1 medmedin2014 2019-07-05 11:21:18 UTC
Created attachment 152576 [details]
OTF Wrong drawings in exported pdf
Comment 2 Roman Kuznetsov 2019-07-06 07:55:59 UTC
Please:
1. Attach your EBGaramond font here
2. Attach sample document in ODT format
3. Add info from Help->About dialog
Comment 3 medmedin2014 2019-07-06 11:44:47 UTC
Created attachment 152597 [details]
source odt + pdf output + version + fonts

Here's the font and the odt file plus the output pdf with screenshot of writer version.
Comment 4 medmedin2014 2019-07-06 11:59:26 UTC
Created attachment 152598 [details]
Scribus sample

And here's a sample of scribus pdf output using the same font, another remark is that writer deforms the output shape of font letters, they are not like scripus output.
Comment 5 QA Administrators 2019-07-07 03:41:04 UTC Comment hidden (obsolete)
Comment 6 Dieter Praas 2019-10-19 09:51:52 UTC
I confirm it with

Version: 6.3.3.1 (x64)
Build-ID: f41f4c7f9507aeca13cb9df51f34d80e8ba30a99
CPU-Threads: 4; BS: Windows 10.0; UI-Render: Standard; VCL: win; 
Gebietsschema: de-DE (de_DE); UI-Sprache: de-DE
Calc: threaded
Comment 7 V Stuart Foote 2019-10-19 13:38:19 UTC
This is a dupe of bug 99114 or bug 105979 where in https://bugs.documentfoundation.org/show_bug.cgi?id=105979#c12 Khaled notes "our subsetter does not support producing CFF fonts" and we get difference between PDF generated by gs printing (embedding CFF font) and our PDF export (embedding PS Type1 font).

Per 105979 this is inherited from OOo where Herbert Dürr (who implmented the CFF -> PS Type1 subsetting) comments in https://bz.apache.org/ooo/show_bug.cgi?id=43029#c88 

Caolán's https://gerrit.libreoffice.org/#/c/47607/ for bug 114704 looks to not have fully resolved issue of bug 105979 but maybe on the right track

Guess the question might be if now, 10 years on, we can fully move to CFF and drop the Type1 subsetting altogether?
Comment 8 V Stuart Foote 2019-10-19 13:39:02 UTC
*** Bug 99114 has been marked as a duplicate of this bug. ***
Comment 9 V Stuart Foote 2019-10-19 13:39:26 UTC
*** Bug 105979 has been marked as a duplicate of this bug. ***