Description: A PDF file generated with Crystal Reports with embedded fonts, is displayed with different fonts when imported by LO Draw 7.2 ++ Steps to Reproduce: 1.Find a PDF file generated with Crystal Reports (attached) 2.Open it with LibreOffice 7.2 or recent build 3.File is displayed with different fonts Actual Results: File is displayed with different fonts, fonts combo box shows wrong font name Expected Results: File must be displayed with same fonts like in any PDF Viewer, Adobe Reader or earlier versions of LibreOffice (7.1 and earlier) Reproducible: Always User Profile Reset: No Additional Info: Version: 7.3.0.0.alpha0+ (x64) / LibreOffice Community Build ID: f58f35b2c8ca1efbacec642a8f3de5b0c499bc6b CPU threads: 4; OS: Windows 10.0 Build 19041; UI render: Skia/Raster; VCL: win Locale: es-MX (es_MX); UI: es-ES Calc: CL
Created attachment 174429 [details] PDF file generated with Crystal Reports
Created attachment 174430 [details] PDF file displayed in Adobe Reader
Created attachment 174431 [details] PDF file displayed in LibreOffice 7.1
Created attachment 174432 [details] PDF file displayed in LibreOfficeDev 7.3 and also in 7.2 release
Seems duplicate. Please search before reporting. *** This bug has been marked as a duplicate of bug 82163 ***
(In reply to Timur from comment #5) > Seems duplicate. Please search before reporting. > > *** This bug has been marked as a duplicate of bug 82163 *** I do not consider this bug as a duplicated of bug 82163, the older bug was present in earlier versions of LibreOffice and was previously fixed as you can see in my LO 7.1 screenshot attachment, so my bug seems as a regresion
"TimesNewRoman" italic is also not a good font. But let's go for a change in 7.2: commit 78d231e25e0984a98622cfc5da7ec26677cd75c2 Date: Fri Jul 23 15:34:36 2021 +0200 source 0ebe806d011b7084b49dd038f3521a03bc935f8c pre 4b5dd477bbe1647c6c60374da2e4cabcf5b6b58b commit 0ebe806d011b7084b49dd038f3521a03bc935f8c [log] author Kevin Suo <suokunlong@126.com> Sat Jul 17 14:25:45 2021 +0800 committer Adolfo Jayme Barrientos <fitojb@ubuntu.com> Fri Jul 23 14:53:03 2021 +0200 tree e6c0e7aaf2507607709759464b3f991b6679b6c0 parent 4b5dd477bbe1647c6c60374da2e4cabcf5b6b58b [diff] sdext.pdfimport: Restore to read font file for the determination... of font attributes, as suggested by Mike Kaganski in https://gerrit.libreoffice.org/c/core/+/118977 This partially reverts da59686672fd2bc98f8cb28d5f04dc978b50ac13 but did some modification of the previous code with some explanationary comments. HI Kevin, please see this.
(In reply to Timur from comment #7) Timur and Gabriel Dorante, if I am understanding correct, this now works correct on master builds (i.e., fonts are shown as "TimesNewRoman" and thus is correctly applied as Times New Roman font by the system), but is broken in 7.2 build (i.e., fonts are shown as "AAAAAA+TimesNewRoman")?
I'm not by computer, but I think not correct in 7.3, fonts shown as as "AAAAAA+TimesNewRoman". This was never Ok, even when fonts were previously shown as as "TimesNewRoman" they were italic, indicating that font was missing and replaced.
I've submitted a patch in https://gerrit.libreoffice.org/c/core/+/120815 Please build and review if it works ok with this patch.
(In reply to Timur from comment #9) > even when fonts were previously shown as as "TimesNewRoman" they were italic, indicating that font was missing and replaced. The font name showning as "TimesNewRoman" rather than "Times New Roman" is a separate issue as explained in bug 143095. However, currently if the font is "TimesNewRoman" in most systems it can be correctly rendered (i.e., substituted) as "Times New Roman", thus this is not a big deal.
Kevin Suo committed a patch related to this issue. It has been pushed to "master": https://git.libreoffice.org/core/commit/a1759769804a7f3b9895b481229d497a9eb4c70a tdf#143959 sdext.pdfimport: fix font name with subtag It will be available in 7.3.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.
Fixed on master, backport to 7.2 branch pending review: https://gerrit.libreoffice.org/c/core/+/120848 Please do help to test to make sure it works without any side effects. If you encounter any issue related to this fix, please comment here.
(In reply to Kevin Suo from comment #8) > (In reply to Timur from comment #7) > Timur and Gabriel Dorante, if I am understanding correct, this now works > correct on master builds (i.e., fonts are shown as "TimesNewRoman" and thus > is correctly applied as Times New Roman font by the system), but is broken > in 7.2 build (i.e., fonts are shown as "AAAAAA+TimesNewRoman")? No, It works correct in 7.1.x builds but is broken in 7.2.x and 7.3.x bulds
Gabriel, it's already fixed, the font name showing as "TimesNewRoman" . It's still italic, meaning replaced, which is another issue. You may test with master from https://dev-builds.libreoffice.org/daily/master/current.html. It installs in addition to your working LO.
Kevin Suo committed a patch related to this issue. It has been pushed to "libreoffice-7-2": https://git.libreoffice.org/core/commit/7c2d2f8fbc8b5751121c7c69dbc0f764ec4cc35e tdf#143959 sdext.pdfimport: fix font name with subtag It will be available in 7.2.1. 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.
Kevin Suo committed a patch related to this issue. It has been pushed to "master": https://git.libreoffice.org/core/commit/2d486bac81e06c64d13c647f35d3f4affbeb183e tdf#143959 sdext.pdfimport: call vcl::Font::identifyFont directly It will be available in 7.3.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.