Download it now!
Bug 94712 - EPSIs don't print to PS or export to PDF properly
Summary: EPSIs don't print to PS or export to PDF properly
Status: NEW
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Printing and PDF export (show other bugs)
Version:
(earliest affected)
Inherited From OOo
Hardware: x86 (IA32) All
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords: filter:pdf
Depends on:
Blocks: PDF-Export
  Show dependency treegraph
 
Reported: 2015-10-02 22:32 UTC by ted.carnevale
Modified: 2019-11-24 10:03 UTC (History)
2 users (show)

See Also:
Crash report or crash signature:


Attachments
files needed to reproduce the bug, and files that demonstrate the bug's effect (29.64 KB, application/zip)
2016-09-12 18:39 UTC, ted.carnevale
Details

Note You need to log in before you can comment on or make changes to this bug.
Description ted.carnevale 2015-10-02 22:32:12 UTC
EPSIs in a Writer document don't print to PS or export to PDF properly. The output file gets only the EPSI's low-res preview bitmap, which is far from satisfactory for any "non-draft" uses. This problem showed up after version 4.1.6.2 and at least as early as 4.2.7.2.
Comment 1 Buovjaga 2015-10-06 11:38:50 UTC
Could you attach an example document?
Does the problem continue in 5.0.x?

Set to NEEDINFO.
Change back to UNCONFIRMED after you have provided the document.
Comment 2 Xisco Faulí 2016-09-11 20:24:48 UTC Comment hidden (obsolete)
Comment 3 ted.carnevale 2016-09-12 18:39:00 UTC
Created attachment 127285 [details]
files needed to reproduce the bug, and files that demonstrate the bug's effect

The attachment is a zip file that contains files that will reproduce the bug and demonstrate the bug's effects. These files were generated and tested under CentOS 6.x (32 bit) and 7.x (64 bit) with the current version of LibreOffice that is standard for these distributions (4.3.7.2), and with current OS updates.  I don't know if it has been fixed in any more recent version of LibreOffice.
Comment 4 Buovjaga 2016-09-13 15:37:16 UTC
You can test with newer versions by this procedure: https://wiki.documentfoundation.org/Installing_in_parallel/Linux
Comment 5 Buovjaga 2016-09-14 17:18:51 UTC
I can reproduce the problem using the sketch.odt. Also by inserting the .epsi file to a new document and exporting.

Are you sure it worked in 4.1.6.2? I get the problematic export already with 3.3, so inherited from OpenOffice.org.

Arch Linux 64-bit, KDE Plasma 5
Version: 5.3.0.0.alpha0+
Build ID: 798d55fcd8efc10fcef6b8ac3fa5abdbc82501ec
CPU Threads: 8; OS Version: Linux 4.7; UI Render: default; 
Locale: fi-FI (fi_FI.UTF-8); Calc: group
Built on September 13th 2016

Arch Linux 64-bit
LibreOffice 3.3.0 
OOO330m19 (Build:6)
tag libreoffice-3.3.0.4
Comment 6 ted.carnevale 2016-09-14 21:44:45 UTC
> Are you sure it worked in 4.1.6.2? I get the problematic export already with 3.3, so inherited from OpenOffice.org.

Quite sure. My private workaround instantiated months ago was to set up a parallel installation of 4.1.6.2. Works for me, but not a practical solution for anyone who is averse to all that custom config stuff. If LibreOffice has any pretensions to being widely useful, necessary functions must simply work. And the ability to deal with encapsulated PostScript is one of those functions.

WRT OO, I did encounter similar symptoms with EPSIs at least once in years past, but those went away. Maybe the most recent problem is a resurrection of that old bug.

I should also mention that OO Impress was able to handle EPSIs quite nicely. That doesn't work with LibreOffice Impress, which is only able to handle bitmaps. It may be that OO Impress merely converted the PostScript to a bitmap without user intervention, but in any case the user didn't have to fiddle around with ghostscript.
Comment 7 Buovjaga 2016-09-15 09:46:21 UTC
Well, I just installed 4.1.6.2 on Windows and I get the problem when exporting to PDF.
Comment 8 theozh 2016-11-16 12:30:47 UTC
"Good" to see that I am not the only one having this problem or wishing an enhancement here.

I cannot remember that the internal PDF-Export of OO and LibO have ever worked correctly with EPS.
Writer just takes the pixelated EPS-Preview as a placeholder (or an empty box if there is no EPS-Preview), which is fine. Sometimes, even the EPS-Preview is displayed not completely and cropped. Which is not so nice.
However, when exporting such an ODT document to PDF, I would clearly expect that Writer takes the vector information of the EPS and includes it somehow in the PDF.
But this is not the case, Writer takes the pixelated preview.

Once, with OO-Writer 3.2.0 under WinXP I had a free "PDF-Printer" who actually included the vector content of the EPS into the PDF. However, a newer version of this "PDF-Printer" did not do the job anymore.

But, come on, please: the PDF-Export of Writer itself should have this functionality.

A suggestion:
Scribus has this functionality. Although, they call this "Embed PDF & EPS files" option "EXPERIMENTAL" it works as far as I have tried. Isn't Scribus also under GPL? Thus, no need to re-invent the wheel...
Comment 9 QA Administrators 2017-11-17 09:09:46 UTC Comment hidden (obsolete)
Comment 10 theozh 2017-11-18 07:41:01 UTC
the bug is still there:
If I include/link an EPS within LibO Writer and export the document as PDF, the vector information of the EPS is NOT included in the PDF.
The result is either an empty place holder frame or the pixelated EPS-preview if it exists.

Version: 5.4.3.2 (x64)
Build-ID: 92a7159f7e4af62137622921e809f8546db437e5
Comment 11 QA Administrators 2018-11-19 03:39:36 UTC Comment hidden (obsolete)
Comment 12 theozh 2018-11-19 07:29:42 UTC
situation unchanged:
Vector information of EPS is not included in exported PDF.
Either the pixelated preview is used or an framed box if EPS has no preview.

Version: 6.1.3.2 (x64)
Build ID: 86daf60bf00efa86ad547e59e09d6bb77c699acb
Comment 13 QA Administrators 2019-11-20 03:50:57 UTC Comment hidden (obsolete)
Comment 14 ted.carnevale 2019-11-24 05:38:24 UTC
Bug is still present, using the latest LibreOffice--6.3.3.2.

Doesn't that mean that its status is "unresolved"?
Comment 15 Buovjaga 2019-11-24 10:03:32 UTC
(In reply to ted.carnevale from comment #14)
> Bug is still present, using the latest LibreOffice--6.3.3.2.
> 
> Doesn't that mean that its status is "unresolved"?

https://wiki.documentfoundation.org/QA/Bugzilla/Fields/Status#How_to_use_NEW