M Henri Day wrote the following on 3/14/2008 3:54 PM:
Jack, that I understand, but presumably the developers who are in the
process of providing the relevant functions in OOo 3 are aware of these
restrictions and are taking them into consideration. Why, then, would an
individual OOo user need to compile OOo him or herself ? Are you - and
Jonathon - suggesting that the OOo developers will for copyright reasons, be
forced to leave the job half done, and that users will have to do the rest
themselves, thereby risking the wrath of Adobe ?...
Henri
Henri,
I'm not saying that the OOo developers will leave anything half done. I
would assume that they, as we do with our own software, will respect
those restrictions that run into the 'gray area' and beyond. I was
simply pointing out that there is no risk to providing features that
would dis-assemble a standard pdf file. Any programmer worth his salt
can bypass the password restriction inside a protected pdf file and let
you gain access. But I'm sure that OOo developers would NOT give you
access to a protected pdf file unless you have the password to gain
access. The same should hold true of bypassing the Reader Extensions.
For non-protected pdf files that are released to the public, there is no
'risk' involved in extracting the content.
--
Jack
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
