From: Ihor Radchenko <yantar92@posteo.net>
To: Max Nikulin <manikulin@gmail.com>
Cc: David Masterson <dsmasterson@gmail.com>, emacs-orgmode@gnu.org
Subject: Re: Exporting Hyperlinks ?
Date: Tue, 07 Nov 2023 12:36:19 +0000 [thread overview]
Message-ID: <87a5rpoi4c.fsf@localhost> (raw)
In-Reply-To: <be3f4624-ed33-4d29-a0a5-06feebeab400@gmail.com>
Max Nikulin <manikulin@gmail.com> writes:
> I just have tried
>
> file-a.tex:
>
> \documentclass{article}
> \usepackage{hyperref}
> \begin{document}
> A 1
>
> \href{file-b.pdf#b-2}{b-2 in file b}
> \newpage
> \section{Section in A}
> \hypertarget{a-2}{}A 2
> \end{document}
>
> file-b.tex:
>
> \documentclass{article}
> \usepackage{hyperref}
> \begin{document}
> B 1
>
> \href{file-a.pdf#a-2}{a-2 in file a}
> \newpage
> \section{Section in B}
> \hypertarget{b-2}{}B 2
> \end{document}
>
> Cross-links between files work.
This is interesting. I am wondering if it is document (it should...).
If \href{file.pdf#anchor} can work, we should indeed use it when
publishing org->pdf.
In particular, we can introduce something similar to
`org-html-link-org-files-as-html', but for pdf export.
--
Ihor Radchenko // yantar92,
Org mode contributor,
Learn more about Org mode at <https://orgmode.org/>.
Support Org development at <https://liberapay.com/org-mode>,
or support my work at <https://liberapay.com/yantar92>
next prev parent reply other threads:[~2023-11-07 12:35 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
2023-11-06 9:37 ` Ihor Radchenko
2023-11-07 12:06 ` Max Nikulin
2023-11-07 12:36 ` Ihor Radchenko [this message]
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=87a5rpoi4c.fsf@localhost \
--to=yantar92@posteo.net \
--cc=dsmasterson@gmail.com \
--cc=emacs-orgmode@gnu.org \
--cc=manikulin@gmail.com \
/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).