Join GitHub today
GitHub is home to over 40 million developers working together to host and review code, manage projects, and build software together.Sign up
Feature request for the future: PDF layers #269
Let me Google that for You.
Standard since PDF specification 1.5.
Present in the UI of every Adobe PDF viewer for about a billion years now.
I'd be more "active" on github (and with other free software) if I enjoyed being slapped about more. (I've stopped using Firefox since the "upgrade" that killed off the truly useful http://code.google.com/p/firefox-mac-pdf/ plugin, which also lacked PDF layer support but otherwise worked very nicely indeed. Browser with no PDF viewing = useless. Safari at least manages that, for all its other crapitude.)
Hey there, didn't mean to insult you! We're doing an issue clean-up, so please forgive closing the issue on you.
And thanks for the detailed response - it definitely clarified what you meant.
Second-guessing terse user requests is a tough thing to do -- did the user mean "layers" at the UI/viewer level, or spec level (optional content), etc? I thought about inquiring here, but I wrongly assumed the odds of a response were low given that your only activity on Github was this comment (we're flattered! :)).
As I said, reopening is definitely an option - consider it done.
I've uploaded a tiny file here that demonstrates broken rendering behavior for optional content groups and/or clipping paths (I'm not sure which thing is actually causing the bad behavior). If you try adding
(This particular PDF came about due to my working on this approach to rendering links in LaTeX using highlighting instead of boxes. The text is rendered into the current clipping path (
an old example with transparency and ocgs, it'd be nice if the ocgs were selectable from within a browser/ page