From: David Masterson <dsmasterson@gmail.com>
To: Max Nikulin <manikulin@gmail.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: Exporting Hyperlinks ?
Date: Wed, 08 Nov 2023 00:02:30 -0800 [thread overview]
Message-ID: <LV8P223MB09207923F06AFAB177024735A2A8A@LV8P223MB0920.NAMP223.PROD.OUTLOOK.COM> (raw)
In-Reply-To: <uidp6q$ds5$1@ciao.gmane.io> (Max Nikulin's message of "Tue, 7 Nov 2023 23:38:50 +0700")
Max Nikulin <manikulin@gmail.com> writes:
> On 07/11/2023 19:36, Ihor Radchenko wrote:
>> If \href{file.pdf#anchor} can work, we should indeed use it when
>> publishing org->pdf.
>
> It would be nice to have a LaTeX package that redefines \label to
> generated \hypertarget from its argument.
This would make it easy to create a PDF "website" that doesn't depend on
a webserver like HTML. A PDF website could easily be put on a USB key
to take with you and access via a mobile phone. This would be secure
because no network interaction. This is the use case I've been working
toward for years.
> Ideally, xr-hyper workflow should be supported as well. A downside is
> anchors are not stable and unrelated to labels.
Stable in the sense that the CUSTOM_ID could be moved to new file?
Could IDs play a roll here?
--
David Masterson
next prev parent reply other threads:[~2023-11-08 8:08 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 [this message]
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=LV8P223MB09207923F06AFAB177024735A2A8A@LV8P223MB0920.NAMP223.PROD.OUTLOOK.COM \
--to=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).