On Sun, 19 Aug 2001, Ralph Bruno wrote:
> Thanks for these suggestions,. I think I've narrowed down the problem to
> font-embedding.
[SNIP]
> Has anyone else successfully converted a FOP pdf to rtf containing embedded
> fonts? Could the problem be in the metrics creation? Or is it possible to
> use the fonts without embedding them?
It's possible to use fonts without embedding them, but unfortunately it
wouldn't help you.
When using multibyte fonts, the glyphs in the document are indexes to the
glyph index in the fontfile. It's possible to use unicode instead of
glyphindexes, but that would require a ToUnicode cmap in the
pdf fontdescriptor. This has been on my todo list for quite some time now,
guess I have to do it... It's not just creating rtf files that won't work,
cut'n'paste from acrobat reader to e.g. word won't work either. More
important: searching your pdf document won't work until ToUnicode cmaps
are implemented.
Tore
>
> Thanks
>
> Ralph Bruno
>
> > -----Original Message-----
> > Sent: 28 July 2001 01:06
> > To: [EMAIL PROTECTED]
> > Subject: Re: pdf security
> >
> > Adobe technical support does exactly what all other
> > big-company support
> > folks do as a first line of defense - blame someone else. In
> > fact, FOP
> > contains precisely zero source code to put an Encrypt key in the PDF
> > document trailer dictionary, and hence it is not possible for
> > documents
> > produced by FOP, out of the box, to have security.
> >
> > If you produce a document with FOP, and look at the document
> > security, not
> > only will it tell you that you can print and copy text to
> > your heart's
> > content, but also that there is no security method.
> >
> > When you say Acrobat 5, I'm guessing you mean Acrobat
> > Exchange. Well, that
> > is the only part of this whole equation that can set
> > security, and so Adobe
> > support lied to you. OK, let's be charitable - they didn't
> > know any better.
> > Given my experience with customer/technical support for big
> > companies that
> > is a very plausible explanation.
> >
> > I'm a bit irritable because I'm just coming off a 12-hour day
> > wrestling with
> > idiosyncracies of a J2EE server which shall go unnamed, and
> > has involved a
> > certain support system for 6 weeks to no avail, so I'm
> > venting a bit at
> > Adobe's expense. They actually deserve the flak to some
> > degree, anyway.
> > Seriously, though, did you inspect the FOP-produced doc using
> > _Reader_? As
> > soon as FOP produced it?
> >
> > Regards,
> > Arved Sandstrom
> >
> > Fairly Senior Software Type
> > e-plicity (http://www.e-plicity.com)
> > Wireless * B2B * J2EE * XML --- Halifax, Nova Scotia
> >
> >
> >
> > At 04:42 PM 7/27/01 +0100, Ralph Bruno wrote:
> > >I'm using FOP 0.19 and Acrobat 5, and whenever I try to export my
> > >FOP-generated pdf to rtf, all I get are seemingly blank
> > pages, but it is in
> > >fact white text on a white background (In case you're
> > wondering, my original
> > >pdf is black, red and grey text on white).
> > >
> > >I contacted Adobe technical support and they've informed me
> > that it's a
> > >result of the security settings in my pdf - it's been set
> > for non-copying of
> > >text. Obviously the only place it could have been set is in
> > the FOP code.
> > >How do I change it to allow copying?
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, email: [EMAIL PROTECTED]
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, email: [EMAIL PROTECTED]
