"Max Nikulin" <[email protected]> writes: > Several years ago I spent some time experimenting with `org-file-apps' > to handle page numbers and search strings for standard "file:" links by > various viewers. That time I was unaware of RFC specs for options to > specify location inside PDF files, see > <https://www.rfc-editor.org/rfc/rfc8118.html#section-3>
Extending this functionality to other viewers may be of great interest, as users may like other non-emacs pdf viewers. As of now, the links only work with pdf-tool (if you're interested, https://github.com/Judafa/linkin-org-pdf-link), I didnt check yet where those four edges format come from (I just reversed engineered pdf-tool's code without asking questions :) ) rn I'm most concerned about basic stuff, which is to get the link format/metadata handling right and versatile for all link usages (file, pdf, music, video, etc). I feel like the format with a plist inside the link is simple and understandable enough, while enabling to encode pretty much anything. But I may be missing something. Julien > On 06/06/2026 2:35 pm, Julien Dallot wrote: >> Here is an example of the pdf link that I use on a daily basis: >> [[pdf:<path>::(:page 12 :edges (0.240196 0.478535 0.331699 0.494949))]] > > Several years ago I spent some time experimenting with `org-file-apps' > to handle page numbers and search strings for standard "file:" links by > various viewers. That time I was unaware of RFC specs for options to > specify location inside PDF files, see > <https://www.rfc-editor.org/rfc/rfc8118.html#section-3> > and the earlier one > <https://www.rfc-editor.org/rfc/rfc3778>. > I have not read referenced ISO and Adobe docs. > > I recall Chromium and Firefox use different base for page coordinates.
