NOTE: use Perl; is on undef hiatus. You can read content, but you can't post it. More info will be forthcoming forthcomingly.
All the Perl that's Practical to Extract and Report
about I/O disciplines and I should retire to the Tassili-in-Aijer
mountains in Sahara as a camel herder :-)
-- Jarkko Hietaniemi
Stories, comments, journals, and other submissions on use Perl; are Copyright 1998-2006, their respective owners.
Just hard (Score:1)
Adobe is certainly not holding the keys tightly. The PDF specification has been wide open almost since the beginning. The problem is more that it's a huge specification and it takes a lot of work to get it right.
I'm the author of CAM::PDF, an open-source library for PDF manipulation. It's a pretty big library, but I only support the very basics of the PDF features. And I'd probably find that I averaged less than minimum wage if I divided the dollars earned on this product by the huge number of hours I'v
Re:Just hard (Score:1)
From what I understand [stackoverflow.com], you must obtain a cryptographic key from an Adobe product to add to the PDF to enable commenting in Adobe Reader. I know the spec is HUGE (I had entertained crazy notions of implementing it but now I know why you need a large team of people to do so). Of course, I very much appreciate everyone's efforts (including your's) to make PDFs available on Linux.
Reply to This
Parent
Re: (Score:1)
Oh, you're right. Weird, I didn't know that Adobe restricted adding annotations. I usually use Apple's bundled Preview.app for annotating PDFs, so I'd never noticed.
I had misunderstood your comment about keys to mean that you needed a key to create a PDF application. Apologies for reading too fast.
Re: (Score:1)
That's quite alright. It is easy to do while reading things on the web.