Bug 100173 - error importing pdf file generated by gis application
Summary: error importing pdf file generated by gis application
Status: NEW
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Draw (show other bugs)
Version:
(earliest affected)
6.2.4.2 release
Hardware: All All
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords: filter:pdf
Depends on:
Blocks: PDF-Import-Draw
  Show dependency treegraph
 
Reported: 2016-06-01 09:57 UTC by Alejandro Vargas
Modified: 2023-07-03 03:11 UTC (History)
4 users (show)

See Also:
Crash report or crash signature:


Attachments
File for testing (252.15 KB, application/pdf)
2016-06-01 09:57 UTC, Alejandro Vargas
Details
stacktrace with symbols from 5.1.3.2 64-bit TDF release (19.89 KB, text/plain)
2016-06-01 13:01 UTC, V Stuart Foote
Details
problem PDF with GIS as opened into Draw (189.16 KB, image/png)
2016-06-01 13:56 UTC, V Stuart Foote
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Alejandro Vargas 2016-06-01 09:57:53 UTC
Created attachment 125443 [details]
File for testing

The PDF includes some drawings that consists on parenthesis inside a box. PDF readers like ghostscript, okular or acrobat reader displays it OK, but Draw imports it as strange characters. 

A PDF file for testing:

https://www.dropbox.com/s/13cdypmgjxanvfa/EJEMPLO.pdf?dl=0

This is how GhostScript and other readers show it:

https://www.dropbox.com/s/18x1094f6mpfr5a/EJEMPLO.png?dl=0

This is how LibreOffice Draw imports it: 

https://www.dropbox.com/s/na2vwcl1gkxn5m8/EJEMPLO_libo.png?dl=0
Comment 1 Samuel Mehrbrodt (allotropia) 2016-06-01 11:10:47 UTC
Confirmed in 5.1.
Comment 2 V Stuart Foote 2016-06-01 13:01:52 UTC
Created attachment 125444 [details]
stacktrace with symbols from 5.1.3.2 64-bit TDF release

Hmm, and Windows builds are not happy trying to parse the PDF with the import filter. Gets hung up.

On Windows 10 Pro 64-bit en-US with 
Version: 5.1.3.2 (x64)
Build ID: 644e4637d1d8544fd9f56425bd6cec110e49301b
CPU Threads: 8; OS Version: Windows 6.19; UI Render: default; 
Locale: en-US (en_US)

Attached a stack-trace.
Comment 3 V Stuart Foote 2016-06-01 13:56:53 UTC
Created attachment 125445 [details]
problem PDF with GIS as opened into Draw

@Alejandro,

Details of your OS and DE?

Also, do things render better in Draw if you disable OpenGL Details of your OS and DE?

On Windows I was not able to get the filter import into Writer to work, with or without OpenGL.

But eventually I did get a clean opening of PDF into Draw, screen clip attached showing marker symbols and fonts well formed. I have Esri ArcGIS 10.4 installed but checking in Acrobat 9.5 shows the Esri fonts *are* sub-setted into the PDF.

And you should be aware that the crop you had applied to the PDF is ignored by LibreOffice, all layers are present for the full sheet.

=-note-=
On Windows 10 Pro 64-bit en-US with 
Version: 5.1.3.2 (x64)
Build ID: 644e4637d1d8544fd9f56425bd6cec110e49301b
CPU Threads: 8; OS Version: Windows 6.19; UI Render: GL; 
Locale: en-US (en_US)
Comment 4 Alejandro Vargas 2016-06-02 06:59:22 UTC
I am testing it in Linux 64 bit. Tested with LireOffice 5.1.0.3 and 4.3.7.2. Just opening with LibreOffice it selects Draw for openning it.

I used Draw for editing PDFs many times with success, but in this case LibreOffice Draw, and other programs like GhostScript, and InkSkape fails to some sections of the PDF.
Comment 5 Alejandro Vargas 2016-06-02 08:31:18 UTC
The problem is the PDF uses an embedded font. :(
Comment 6 QA Administrators 2017-09-01 11:20:13 UTC Comment hidden (obsolete)
Comment 7 Roman Kuznetsov 2018-07-01 00:31:20 UTC
still present in LO 6.1 beta 2, but brown shapes shows different from its view in 5.1
Comment 8 QA Administrators 2019-07-02 02:43:06 UTC Comment hidden (obsolete)
Comment 9 Alejandro Vargas 2019-07-02 10:30:14 UTC
The problem is not solved yet. Checked with current version of Libreoffie Draw.
Comment 10 V Stuart Foote 2019-07-02 12:56:55 UTC
Correct, the poppler based import filter has considerable trouble with the clipped PDF, setting scale, clip masking, and use of embedded fonts in transforming the PDF objects to Draw objects.

Otherwise the pdfium based insert filter generates a bitmap to canvas with very high fidelity currently at a fixed 96dpi, but it likewise fails on "break" of the PDF objects out to Draw objects.

So, while the import filter remains of limited use against these GIS maps, the pdfium based insert as image is the much more common use case and is quite functional.

IMHO => WF as the other BZ issues with the poppler import filter are sufficient.
Comment 11 QA Administrators 2021-07-02 03:42:30 UTC Comment hidden (obsolete)
Comment 12 QA Administrators 2023-07-03 03:11:50 UTC
Dear Alejandro Vargas,

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