Bug 78427 - FILEOPEN PDF Import: sometimes bold and italic font properties are imported incorrectly
Summary: FILEOPEN PDF Import: sometimes bold and italic font properties are imported i...
Status: NEW
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Draw (show other bugs)
Version:
(earliest affected)
4.3.0.0.alpha0+ Master
Hardware: Other All
: medium normal
Assignee: Not Assigned
URL:
Whiteboard: target:4.3.0
Keywords:
Depends on:
Blocks: PDF-Import-Draw
  Show dependency treegraph
 
Reported: 2014-05-08 08:49 UTC by vvort
Modified: 2019-11-19 10:20 UTC (History)
2 users (show)

See Also:
Crash report or crash signature:


Attachments
Test file 1 (23.21 KB, application/pdf)
2014-05-08 08:49 UTC, vvort
Details
Test file 2 (4.98 KB, application/pdf)
2014-05-08 08:50 UTC, vvort
Details
info fonts acrobat reader of file 1 (18.33 KB, image/png)
2018-08-25 11:04 UTC, paulystefan
Details
info fonts acrobat reader of file 2 (16.65 KB, image/png)
2018-08-25 11:05 UTC, paulystefan
Details
506_Vorsorgevollmacht.pdf (73.78 KB, application/pdf)
2019-11-19 10:17 UTC, DerMartin
Details

Note You need to log in before you can comment on or make changes to this bug.
Description vvort 2014-05-08 08:49:56 UTC
Created attachment 98668 [details]
Test file 1

Here is two examples:
1. Bold property is specified, but text is imported as normal.
2. Bold italic text is imported as italic text.
Comment 1 vvort 2014-05-08 08:50:50 UTC
Created attachment 98669 [details]
Test file 2
Comment 2 vvort 2014-05-08 08:59:54 UTC
Example #2 is fixed here:
https://gerrit.libreoffice.org/9276
Comment 3 Commit Notification 2014-05-08 09:05:24 UTC
Vort committed a patch related to this issue.
It has been pushed to "master":

http://cgit.freedesktop.org/libreoffice/core/commit/?id=e0bde4c53b1b8412833d4b84a214da8b8fc1f6e7

fdo#78427 PDF Import: Improve detection of bold italic font



The patch should be included in the daily builds available at
http://dev-builds.libreoffice.org/daily/ in the next 24-48 hours. More
information about daily builds can be found at:
http://wiki.documentfoundation.org/Testing_Daily_Builds
Affected users are encouraged to test the fix and report feedback.
Comment 4 Kevin Suo 2014-07-24 12:09:40 UTC
added bug 81484 as see also.
Comment 5 QA Administrators 2015-09-04 02:49:35 UTC Comment hidden (obsolete)
Comment 6 Alexander Tselikov 2016-02-05 10:32:45 UTC
(In reply to QA Administrators from comment #5)
> ** Please read this message in its entirety before responding **
> 
> 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 on a currently supported version of
> LibreOffice (5.0.0.5 or later)
>    https://www.libreoffice.org/download/
> 
>    If the bug is present, please leave a comment that includes the version
> of LibreOffice and your operating system, and any changes you see in the bug
> behavior
>  
>  If the bug is NOT present, please set the bug's Status field to
> RESOLVED-WORKSFORME and leave a short comment that includes your version of
> LibreOffice and Operating System
> 
> 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)
> 
> http://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:
> http://webchat.freenode.net/?channels=libreoffice-qa
> 
> Thank you for your help!
> 
> -- The LibreOffice QA Team This NEW Message was generated on: 2015-09-03

Case 1 still reproducing.

Version: 5.0.4.2
Build ID: 1:5.0.4~rc2-0ubuntu1~trusty1
Locale: en-US (en_US.UTF-8)
Linux Mint 17.3
Comment 7 Heiko Tietze 2016-05-10 10:03:21 UTC
Confirmed

Version: 5.2.0.0.alpha0+
Build ID: 6b232aeecc55f1715bc111e636e36a8e24827efb
CPU Threads: 4; OS Version: Windows 6.1; UI Render: default; 
TinderBox: Win-x86@39, Branch:master, Time: 2016-01-26_07:40:04
Locale: de-DE (de_DE)
Comment 8 QA Administrators 2017-09-01 11:20:10 UTC Comment hidden (obsolete)
Comment 9 Kevin Suo 2017-09-02 00:11:59 UTC
Bug still exists in the most recent version.
Comment 10 paulystefan 2017-11-27 20:55:07 UTC
5.4.3.2 x64 win 10

bug present in test file 1
Comment 11 paulystefan 2018-08-25 11:04:35 UTC
Created attachment 144421 [details]
info fonts acrobat reader of file 1

different fonts in files 

truetype and type1 in first and truetype only in second file
Comment 12 paulystefan 2018-08-25 11:05:10 UTC
Created attachment 144422 [details]
info fonts acrobat reader of file 2

different fonts in files 

truetype and type1 in first and truetype only in second file
Comment 13 paulystefan 2019-08-23 21:28:21 UTC
same problem in 6.3.0.4 with different fonts in relation to acro reader
Comment 14 DerMartin 2019-11-19 10:15:22 UTC
Attached file "506_Vorsorgevollmacht.pdf" has probably the same issue.
Comment 15 DerMartin 2019-11-19 10:17:06 UTC
Created attachment 155937 [details]
506_Vorsorgevollmacht.pdf
Comment 16 DerMartin 2019-11-19 10:20:02 UTC
LO version 6.3.3.2.0+