Skip to content
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

Open
davelab6 opened this issue May 16, 2018 · 6 comments
Open

Provide PDF as release #2

davelab6 opened this issue May 16, 2018 · 6 comments
Assignees

Comments

@davelab6
Copy link

GitHub release pages can be used to distribute binary PDFs built at specific commits of the source :)

@jvasile
Copy link
Member

jvasile commented May 16, 2018

That's a good idea. We'll get on it.

@kfogel
Copy link
Member

kfogel commented Mar 17, 2019

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.

@kfogel kfogel self-assigned this Mar 17, 2019
@kfogel
Copy link
Member

kfogel commented Oct 28, 2019

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 \label{archetype:b2b-open-source} on that subsection).

@choeppler
Copy link

choeppler commented Oct 29, 2019

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 \hypertarget{archetype:b2b-open-source}{} instead of or in addition to the label command, according to this post on TeX - LaTeX Stack Exchange.

@kfogel
Copy link
Member

kfogel commented Oct 29, 2019

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 hyperref package, but hadn't yet figured out about the need for \hypertarget in the source.

I'll try it! More here soon.

kfogel added a commit that referenced this issue Oct 29, 2019
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.
@kfogel
Copy link
Member

kfogel commented Oct 29, 2019

Update: it works!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants