From: Max Nikulin <manikulin@gmail.com>
To: emacs-orgmode@gnu.org
Subject: Re: Exporting Hyperlinks ?
Date: Fri, 3 Nov 2023 17:44:17 +0700 [thread overview]
Message-ID: <ui2iu4$5a1$1@ciao.gmane.io> (raw)
In-Reply-To: <LV8P223MB0920CAA6DB6B5FCC84C67ECBA2A5A@LV8P223MB0920.NAMP223.PROD.OUTLOOK.COM>
On 03/11/2023 13:29, David Masterson wrote:
> the generated LaTeX href looks like
>
> \href{contacts.tex}{My text}
>
> which looks wrong.
Search part definitely should be retained.
I have realized that in the LaTeX world inter-document cross-linking
works differently. With the xr-hyper package, labels from another
document may be used directly or with a prefix:
https://texfaq.org/FAQ-extref
It may be implemented for Org random labels.
However I would strongly prefer PDF files having stable anchors based on
CUSTOM_ID, not ones derived from section, figure, etc. counters. I am
unsure if there is a package that allows to get such anchors out of the box.
When I looked into the code for link targets resolution in the context
of ox-html, I found it rather complicated.
> I use publish for LaTex (org-latex-publish-to-pdf)
Depending on your requirements, it might be possible to export to HTML
files and then print them to PDF as a workaround. Chromium supports
headless printing, so it should be scriptable. However to improve
quality of formatting almost certainly heavy customization of CSS.
I have realized that Chomium scrolls to proper position in PDF when it
opens a file URI with #anchor part, but it does not update tab address
bar when an internal link is clicked and it does not react when URL is
edited to change #anchor part.
next prev parent reply other threads:[~2023-11-03 10:45 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 [this message]
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
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='ui2iu4$5a1$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).