On Mon, 2007-05-21 at 22:20 +0300, =?UTF-8?Q? Martin-=C3=89ric?= Racine wrote: > On 5/21/07, Volker Christian Behr <[EMAIL PROTECTED]> wrote: > > Hi, this is upstream, > > > > I can reproduce this issue if you use exotic fonts in OpenOffice. Using > > Arial for example the output is perfectly searchable by a PDF-viewer. > > > > I have to check why GS does not simply replace the font by some other it > > knows (or what exactly is causing the issue, if not the font unknown to > > GS). > > > > Martin-Eric, could you please re-tag this to 'wishlist' since it > > technically is not a bug in CUPS-PDF (CUPS-PDF working as designed) but > > rather in the conversion done by GS (maybe some additional option will > > help). > > Volker, since this is strictly-speaking a GS bug, I'm wondering if > reassigning it to GS might make more sense? > > However, one part of the report attracted my attention: the user > successfully creates searchable documents when exporting to PDF > directly in OpenOffice. I wonder how their PDF implementation differs > from the one used by CUPS? > If they implement the PDF generation directly into OpenOffice, they won't run into any unknown-font-issues.... as I tested: CUPS-PDF creates perfectly searchable documents when a font like Arial is used.
-- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
