<html> <head> <base href="https://bugs.documentfoundation.org/" /> </head> <body> <div> <a class="bz_bug_link bz_status_NEW " title="NEW - EPS rendering: locating pstoedit on Mac a problem" href="https://bugs.documentfoundation.org/show_bug.cgi?id=67465#c25">Comment # 25</a> on <a class="bz_bug_link bz_status_NEW " title="NEW - EPS rendering: locating pstoedit on Mac a problem" href="https://bugs.documentfoundation.org/show_bug.cgi?id=67465">bug 67465</a> from <a class="email" href="mailto:vstuart.foote@utsa.edu" title="V Stuart Foote <vstuart.foote@utsa.edu>"> V Stuart Foote</a> <pre>(In reply to Robert R. Howell from <a href="show_bug.cgi?id=67465#c23">comment #23</a>) Well the obvious thing is to simply break the path to pstoedit, or uninstall it. And to insure that ghostscript (or Imagemagick convert) is on path to perform the RenderAsBMP preview. With its very low quality rendering to EMF/WMF, pstoedit is really of questionable utility. It is not clear if the pstoedit paid EMF plugin improves things. Simply don't use it--then no need for an environment variable switch. The bigger issue for scientific and technical publication (once poor quality EMF/WMF preview rendering is removed) is that the substitute preview BMP is rendered at 300dpi. And those raster previews, while fine for on screen use, are passed out for printing or embedding into ps or PDF ( <a class="bz_bug_link bz_status_NEW " title="NEW - PRINTING: to PDF with Adobe Distiller or GS based PDF printer, EPS images not rendered to PS vector for PDF, instead print uses the preview of EPS image" href="show_bug.cgi?id=81497">bug 81497</a> ) with loss of vector graphic quality needed for publication. Likewise, for EPS images with embedded TIFF previews--those low resolution previews are used as the RenderAsBMP is never called to regenerate them. And the original preview is passed for ps or PDF generation. Replacement of the preview might be worthwhile to implement for on screen use.</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are on the CC list for the bug.</li> </ul> </body> </html>