Bug 104725 - the bold face word in .pdf are not properly showed in LibO Draw
Summary: the bold face word in .pdf are not properly showed in LibO Draw
Status: RESOLVED DUPLICATE of bug 81484
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Writer (show other bugs)
Version:
(earliest affected)
5.3.0.0.beta2
Hardware: x86 (IA32) Windows (All)
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2016-12-17 09:26 UTC by j54311543
Modified: 2016-12-18 19:07 UTC (History)
3 users (show)

See Also:
Crash report or crash signature:

Attachments
the problem can be easily distinguish in the picture (215.21 KB, image/png)
2016-12-17 09:28 UTC, j54311543 		Details
View All Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description j54311543 2016-12-17 09:26:39 UTC 
Description:
If you open a pdf file within bold face words inside, the bold face words will become hollow in the pdf editor of libreoffice.

Steps to Reproduce:
1.create a pdf file within bold face words inside
2.open the file in pdf editor in libreoffice
3.then the problem is reproduced

Actual Results:  
The words are not as same as the words show in the original pdf file.

Expected Results:
The words should be as same as the words showed in pdf file.


Reproducible: Always

User Profile Reset: No

Additional Info:


User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:50.0) Gecko/20100101 Firefox/50.0
Comment 1 j54311543 2016-12-17 09:28:19 UTC 
Created attachment 129708 [details]
the problem can be easily distinguish in the picture

same as the title
Comment 2 tommy27 2016-12-17 13:06:17 UTC 
please upload the problematic PDF file and a screenshot of how the file is supposed to be displayed.
Comment 3 V Stuart Foote 2016-12-17 15:29:43 UTC 
Can not reproduce round trip from LibreOffice Writer -> export PDF -> import filter open in Draw

What font was used, and how was the PDF prepared?
Comment 4 Buovjaga 2016-12-18 19:07:04 UTC 

*** This bug has been marked as a duplicate of bug 81484 ***