-
Notifications
You must be signed in to change notification settings - Fork 12
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Provide PDF as release #2
Comments
That's a good idea. We'll get on it. |
See the discussion in issue #9 and issue #7, though: we may move to HTML as the primary source, and the PDF would be a manually-designed job probably done by one of Mozilla's excellent designers (who did the v1 PDF). I suppose we could still distribute it as a "built binary", although that would be a bit of a fiction in this case. |
Also related to issues #9 and #7: In case we decide to stick with a LaTeX-first workflow and PDF as the main release, I've been doing a little research into how one can deep-link directly into a PDF. The short answer seems to be: it's easy to do by page number, but harder to do by arbitrary ID (what's hard about the latter is not so much how to deep-link to a particular ID if you have it, but more how to reliably generate the IDs in the PDF from the LaTeX source in the first place). For example, I can link to: file:///home/kfogel/blah/blah/open-source-archetypes.pdf#page=10 and my browser (both Firefox and Chromium) will DTRT. But if I try it this way: file:///home/kfogel/blah/blah/open-source-archetypes.pdf#archetype:b2b-open-source ...it doesn't work, I think because that label isn't actually in the PDF (even though it's in the LaTeX with a |
Seems you can link either to a specific page, or to a named destination (cf. e.g. Adobe's Parameters for opening PDF files; notes on URLs on pp. 7 f.) To create a named destination in the pdf you'd need |
Why, hello there, @choeppler! And yes -- thank you; my own experiments were just leading me to that, but I'll get there faster thanks to your message. I'd figured out that we need the I'll try it! More here soon. |
Thanks to Chris Hoeppler (@choeppler) for suggesting this in his comment of October 28th in issue #2. Note that this requires the 'hyperref' package, which is now included (as of commit 1ae5bfe9a) via 'ots-doctools', on which this build already depends.
Update: it works! |
GitHub release pages can be used to distribute binary PDFs built at specific commits of the source :)
The text was updated successfully, but these errors were encountered: