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:
Created attachment 152576 [details] OTF Wrong drawings in exported pdf
Please: 1. Attach your EBGaramond font here 2. Attach sample document in ODT format 3. Add info from Help->About dialog
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.
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.
[Automated Action] NeedInfo-To-Unconfirmed
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
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?
*** Bug 99114 has been marked as a duplicate of this bug. ***
*** Bug 105979 has been marked as a duplicate of this bug. ***
Dear medmedin2014, To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://web.libera.chat/?settings=#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug
This bug is still present in Version: 7.2.6.2 / LibreOffice Community Build ID: 20(Build:2) CPU threads: 8; OS: Linux 5.13; UI render: default; VCL: kf5 (cairo+xcb) Locale: de-DE (de_DE.UTF-8); UI: de-DE Ubuntu package version: 1:7.2.6-0ubuntu0.21.10.1 Calc: threaded
Repro on: Version: 7.4.0.0.alpha0+ / LibreOffice Community Build ID: e4243a140345a4bcd800217115b42667e277c6a3 CPU threads: 2; OS: Linux 5.17; UI render: default; VCL: kf5 (cairo+xcb) Locale: en-US (en_US.UTF-8); UI: en-US Calc: threaded
Khaled Hosny committed a patch related to this issue. It has been pushed to "master": https://git.libreoffice.org/core/commit/a387f39de8e59d7542b74962242504b798af1362 tdf#126242: Handle fractional values when subsetting CFF It will be available in 7.5.0. The patch should be included in the daily builds available at https://dev-builds.libreoffice.org/daily/ in the next 24-48 hours. More information about daily builds can be found at: https://wiki.documentfoundation.org/Testing_Daily_Builds Affected users are encouraged to test the fix and report feedback.
Khaled Hosny committed a patch related to this issue. It has been pushed to "libreoffice-7-4": https://git.libreoffice.org/core/commit/81fe821cc30a6746636350d78b4fdd88839dc21c tdf#126242: Handle fractional values when subsetting CFF It will be available in 7.4.3. The patch should be included in the daily builds available at https://dev-builds.libreoffice.org/daily/ in the next 24-48 hours. More information about daily builds can be found at: https://wiki.documentfoundation.org/Testing_Daily_Builds Affected users are encouraged to test the fix and report feedback.
Fix verified in: Version: 7.5.0.0.alpha1+ (X86_64) / LibreOffice Community Build ID: ad085990b8073a122ac5222e5220f8f1d6826dcf CPU threads: 8; OS: Linux 5.15; UI render: default; VCL: gtk3 Locale: en-AU (en_AU.UTF-8); UI: en-US Calc: threaded Thanks Khaled!
Many characters were fixed, but some are still having minor issues in the output PDF. See attached new file. Version: 7.5.0.3 (X86_64) / LibreOffice Community Build ID: 50(Build:3) CPU threads: 2; OS: Linux 6.1; UI render: default; VCL: kf5 (cairo+xcb) Locale: en-US (en_US.UTF-8); UI: en-US 7.5.0-1 Calc: threaded Operating System: Manjaro Linux KDE Plasma Version: 5.26.5 KDE Frameworks Version: 5.103.0 Qt Version: 5.15.8 Kernel Version: 6.1.12-1-MANJARO (64-bit) Graphics Platform: X11
Created attachment 185953 [details] Font distortion
This is a different font and a different issue than the original report (specifically, these glyphs do not use fractional coordinates). Please open a new issue.
I tried to verify the basic 26 letters, only the letter "v" still have a problem.
Created attachment 186050 [details] letter "v"
Created attachment 186051 [details] PDF exported from 7.5 (In reply to medmedin2014 from comment #20) > Created attachment 186050 [details] > letter "v" I can reproduce this. Lower case v looks fine in PDF and the font extracted from PDF looks fine in FontForge.
(In reply to خالد حسني from comment #21) > Created attachment 186051 [details] > PDF exported from 7.5 > > (In reply to medmedin2014 from comment #20) > > Created attachment 186050 [details] > > letter "v" > > I can reproduce this. Lower case v looks fine in PDF and the font extracted > from PDF looks fine in FontForge. I *can’t* reproduce.
Created attachment 186052 [details] Letter "v" I opened your attached pdf with Firefox and Chromium built-in PDF readers, and with Okular (poppler based) and all show a distortion in letter "v", only MuPDF reader shows correctly the letter.
Created attachment 186054 [details] Letter v in Chrome, Acrobat Reader, Firefox, Master PDF Editor, Inkscape, and FontForge I tested with Letter v in Chrome, Acrobat Reader, Firefox, Master PDF Editor, Inkscape, and extracted the font from PDF and opened it on FontForge. I can only reproduce with Inkscape and another tool (not shown here) that uses FreeType, so my guess would be a bug in FreeType and I suggest you report the issue there (you can extract the font from the PDF with “mutool extract”).
If you get any evidence from FreeType developers that this is a LibreOffice bug, please re-open.
You can also test the extracted font with ftview. The issue is reproducible when hinting is off (press h to toggle hinting on/off).