Date: prev next · Thread: first prev next last
2015 Archives by date, by thread · List index


https://bugs.documentfoundation.org/show_bug.cgi?id=67465

--- Comment #27 from V Stuart Foote <vstuart.foote@utsa.edu> ---
(In reply to Robert R. Howell from comment #26)
... doesn't work in practice for most users because
it breaks other software packages which rely on pstoedit.  

Well on OS X or Windows that is not an issue--pstoedit is not routinely
installed (nor is Imagemagick, nor ghostscript). And, few Linux distros bundle
pstoedit by default. So, which other software (on Linux) do you perceive as
pstoedit dependent?  But guess if one has to have it for something substantive,
might not be viable to hide it from path.

... If there's a way
to just remove it from the LibreOffice path could you let me know?  But that
still is a much more obscure fix for most users than simply providing an
option to explicitly set the renderer preference.

No, your suggested environment approach would be the only way to toggle between
WMF/EMF vector previews via pstoedit and "native" BMP rasters via Ghostscript
or Imagemagick convert.

Personally, the pstoedit EMF vector previews in LibreOffice are of such low
quality, I'd prefer elimination of the RenderAsEMF methods [1] until a better
option for vector previews can be implemented.

=-ref-=
[1]
http://opengrok.libreoffice.org/xref/core/filter/source/graphicfilter/ieps/ieps.cxx#196

-- 
You are receiving this mail because:
You are on the CC list for the bug.

Context


Privacy Policy | Impressum (Legal Info) | Copyright information: Unless otherwise specified, all text and images on this website are licensed under the Creative Commons Attribution-Share Alike 3.0 License. This does not include the source code of LibreOffice, which is licensed under the Mozilla Public License (MPLv2). "LibreOffice" and "The Document Foundation" are registered trademarks of their corresponding registered owners or are in actual use as trademarks in one or more countries. Their respective logos and icons are also subject to international copyright laws. Use thereof is explained in our trademark policy.