2008/3/14, Jack D. Lewis <[EMAIL PROTECTED]>: > > jonathon wrote the following on 3/14/2008 12:32 PM: > > > On Fri, Mar 14, 2008 at 11:21 AM, M Henri Day > > > > > >> Jonathon, could I prevail upon you to explain ? I don't think > >> > > > > Risk assessment > > > > xan > > > > jonathon > > > > > There are certain areas of PDF development that programmers have to be > careful of not 'treading upon' - ie: Tampering with the Reader > Extensions that implement user rights. However, the rest of the PDF > format specifications are publicly available for developers to implement > their own solutions. > > From Adobe's own site @ > http://www.adobe.com/devnet/pdf/pdf_reference.html: "This book provides > a description of the PDF file format and is intended primarily for > developers of /PDF producer/ applications that create PDF files > directly. It also contains enough information to allow developers to > write /PDF consumer/ applications that read existing PDF files and > interpret or modify their contents." > > The book can be downloaded here: > http://www.adobe.com/devnet/acrobat/pdfs/pdf_reference_1-7.pdf > > -- > > Jack
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
