From: Max Nikulin <manikulin@gmail.com>
To: emacs-orgmode@gnu.org
Subject: Re: Exporting Hyperlinks ?
Date: Wed, 8 Nov 2023 17:50:19 +0700 [thread overview]
Message-ID: <uifp5d$g5n$1@ciao.gmane.io> (raw)
In-Reply-To: <87h6lwfuvh.fsf@localhost>
On 08/11/2023 16:37, Ihor Radchenko wrote:
> Max Nikulin writes:
>
>> It would be nice to have a LaTeX package that redefines \label to
>> generated \hypertarget from its argument.
>
> Can't we simply generate a pair of \label + \hypertarget when generating
> .tex files in ox-latex? This way, we can make sure that labels in
> Org-generated pdfs will be linkable from outside world.
I still have a hope that somebody can point us how to leverage hyperref
facilities. Adding \hypertarget is a step forward, but ideally internal
links generated by \ref, links in table of contents, PDF bookmarks
(table of contents side bar) should consistently use #custom_id anchors
as well. Usual #section.5 should be a fallback for cases with no user
supplied labels.
> I think that generating \hypertarget + converting .org file links to
> .pdf links will already be a good improvement.
>
> Using xr-hyper requires knowledge of external files we link to and thus
> can only be used during publishing, where we have all the information
> about multiple exported Org documents available.
I agree that some complications exist. Just like with HTML files for Org
ones with <file:another.org::*heading> links. Several iterations of tex
files compilation are required. .aux files for all .tex files must be
available to get cross-file links working.
prev parent reply other threads:[~2023-11-08 10:51 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
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 [this message]
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='uifp5d$g5n$1@ciao.gmane.io' \
--to=manikulin@gmail.com \
--cc=emacs-orgmode@gnu.org \
/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).