From: David Masterson <dsmasterson@gmail.com>
To: Ihor Radchenko <yantar92@posteo.net>
Cc: Max Nikulin <manikulin@gmail.com>, emacs-orgmode@gnu.org
Subject: Re: Exporting Hyperlinks ?
Date: Sun, 05 Nov 2023 14:28:34 -0800 [thread overview]
Message-ID: <LV8P223MB09206E3F5D00BFFD85E8AC5EA2ABA@LV8P223MB0920.NAMP223.PROD.OUTLOOK.COM> (raw)
In-Reply-To: <87y1fc4bog.fsf@localhost> (Ihor Radchenko's message of "Sun, 05 Nov 2023 12:38:55 +0000")
Ihor Radchenko <yantar92@posteo.net> writes:
> Max Nikulin <manikulin@gmail.com> writes:
>
>> Human-readable link targets are susceptible to collisions. So ox-latex
>> should support links to particular locations in the specified files,
>> either an Org one or inside external PDF files. Code from ox-html should
>> be adapted for ox-latex.
>>
>> [[file:test.pdf::#anchor][Another document]]
>> -> \href{test.pdf\#anchor}{Another document}
>
> AFAIK, this kind of URL cannot be opened except when opening pdf in
> browser.
What else is there? PDFviewer? What is the standard for Latex?
>> [[file:test.org::#anchor][Another document]]
>> Either for xr-hyper
>> -> Another document \ref{f1-orgabc123}
>> with \label{orgabc123} in test.tex
>> or with redefined \label to generate additional \hypertarget
>> -> \href{test.pdf\#anchor}{Another document}
>
> And this does not fit into single-document exports. We must export
> multiple files via ox-publish. ...and ox-publish does not support pdf
> export.
org-latex-publish-to-pdf ?? Oh, you mean that it has to go through
Latex to get to PDF.
--
David Masterson
next prev parent reply other threads:[~2023-11-05 22:34 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-01 4:24 Exporting Hyperlinks ? David Masterson
2023-11-01 16:36 ` Max Nikulin
2023-11-02 2:11 ` David Masterson
2023-11-02 15:24 ` Max Nikulin
2023-11-03 6:29 ` David Masterson
2023-11-03 10:44 ` Max Nikulin
2023-11-03 21:55 ` Samuel Wales
2023-11-03 22:06 ` Samuel Wales
2023-11-03 22:07 ` Samuel Wales
2023-11-04 7:10 ` Max Nikulin
2023-11-05 12:38 ` Ihor Radchenko
2023-11-05 22:28 ` David Masterson [this message]
2023-11-06 9:37 ` Ihor Radchenko
2023-11-07 12:06 ` Max Nikulin
2023-11-07 12:36 ` Ihor Radchenko
2023-11-07 16:38 ` Max Nikulin
2023-11-08 8:02 ` David Masterson
2023-11-08 10:39 ` Max Nikulin
2023-11-08 9:37 ` Ihor Radchenko
2023-11-08 10:50 ` Max Nikulin
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=LV8P223MB09206E3F5D00BFFD85E8AC5EA2ABA@LV8P223MB0920.NAMP223.PROD.OUTLOOK.COM \
--to=dsmasterson@gmail.com \
--cc=emacs-orgmode@gnu.org \
--cc=manikulin@gmail.com \
--cc=yantar92@posteo.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).