emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: David Masterson <dsmasterson@gmail.com>
To: Max Nikulin <manikulin@gmail.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: Exporting Hyperlinks ?
Date: Thu, 02 Nov 2023 23:29:46 -0700	[thread overview]
Message-ID: <LV8P223MB0920CAA6DB6B5FCC84C67ECBA2A5A@LV8P223MB0920.NAMP223.PROD.OUTLOOK.COM> (raw)
In-Reply-To: <ui0ev0$elj$1@ciao.gmane.io> (Max Nikulin's message of "Thu, 2 Nov 2023 22:24:14 +0700")

Max Nikulin <manikulin@gmail.com> writes:

> On 02/11/2023 09:11, David Masterson wrote:
>> If I understand what you mean by "anchor", does Org create an anchor in
>> exporting to Latex when it sees a CUSTOM_ID property in an item?  Then,
>> would the search in the hyperlink reference the anchor?  Your examples
>> weren't precise enough for me to follow.
>
> You are right. Despite `org-latex-prefer-user-labels' exists, it
> currently affects LaTeX label names only, so it is possible to
> reference them as #page.2, #section.3, but not as
> #custom_id. ox-beamer however adds \hypertarget{anchor}... for Org
> <<anchor>>, so in PDF it can be referenced as #anchor.
>
> So ox-latex should be improved to add \hypertarget commands for CUSTOM_ID.

I agree.  For a link of:

  [[file:contacts.org::#custom_id][My text]]

the generated LaTeX href looks like

  \href{contacts.tex}{My text}

which looks wrong.

> Originally I suspected only issues with links.
>
> To get links between HTML documents where CUSTOM_ID are not used, it
> is necessary to rely on org-publish to track autogenerated anchors. I
> am unsure if publish works for LaTeX.

I use publish for LaTex (org-latex-publish-to-pdf)

-- 
David Masterson


  reply	other threads:[~2023-11-03  6: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 [this message]
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

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=LV8P223MB0920CAA6DB6B5FCC84C67ECBA2A5A@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).