Bug 79047 - PDF Import: Imported page difficult to read
Summary: PDF Import: Imported page difficult to read
Status: RESOLVED DUPLICATE of bug 92924
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Draw (show other bugs)
(earliest affected) release
Hardware: All All
: medium normal
Assignee: Not Assigned
Depends on: 86211
  Show dependency treegraph
Reported: 2014-05-22 02:21 UTC by Biju
Modified: 2016-05-10 09:21 UTC (History)
3 users (show)

See Also:
Crash report or crash signature:

Screenshot with LO Draw 4.3.0 (182.60 KB, image/png)
2014-07-14 09:02 UTC, Alexandr
Screenshot with Okular (159.04 KB, image/png)
2014-07-14 09:03 UTC, Alexandr

Note You need to log in before you can comment on or make changes to this bug.
Description Biju 2014-05-22 02:21:45 UTC
+++ This bug was initially created as a clone of Bug #78807 +++

Build ID: da739f729223908516deb1c2564d0713231abb5b
Tested on WinXP

Imported page difficult to read
See Page 1 

Actual : attachment 99196 [details] page_1_LO.PNG

Expected : attachment 99197 [details] page_1_FF.PNG
Comment 1 tommy27 2014-06-18 02:37:48 UTC
reproducible under Win7x64 using LibO
status NEW
Comment 2 Alexandr 2014-07-14 09:02:44 UTC
Created attachment 102753 [details]
Screenshot with LO Draw 4.3.0

The situation is better in LibreOffice the text is mostly readable, but the picture is still destroyed. I tried it on Debian Jessie x86_64 so, I set platform to “All”.
I am not sure that Firefox (“Expected” variant in initial message) displays the page correctly. Okular and Evince represent the picture in another way.
Comment 3 Alexandr 2014-07-14 09:03:29 UTC
Created attachment 102754 [details]
Screenshot with Okular
Comment 4 Biju 2014-09-09 02:28:26 UTC
(In reply to comment #2)
> The situation is better in LibreOffice the text is mostly readable,


> I am not sure that Firefox (“Expected” variant in initial message) displays
> the page correctly. Okular and Evince represent the picture in another way.

you may be right
Comment 5 vvort 2014-11-12 16:21:49 UTC
Some of the problems with this document can be fixed by implementing clipping ( Bug 86211 )
Comment 6 QA Administrators 2015-12-20 16:15:18 UTC
** 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.4 or later)

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
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)


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-12-20
Comment 7 Heiko Tietze 2016-05-10 09:21:39 UTC
Transparency issue is reported for export in 92924 and import in 44729, for example.

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