emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Max Nikulin <manikulin@gmail.com>
To: emacs-orgmode@gnu.org
Subject: Re: Internal link broken when publishing (was org-id with ox-html)
Date: Mon, 20 Sep 2021 21:13:24 +0700	[thread overview]
Message-ID: <sia4u6$10ll$1@ciao.gmane.io> (raw)
In-Reply-To: <51009862.OmzxVWrqTf@pluto>

On 20/09/2021 07:05, chris wrote:
> On Tuesday, 14 September 2021 18:33:43 CEST Max Nikulin wrote:
>> As a kind of summary:
>> During publishing of a project
>> - "id:" links to headings from the same file are exported as short
>> generated anchors like #org032777e or as anchors to custom ids when the
>> latter are available
>> - "Search heading" links to other files are exported as short generated
>> anchors or as custom ids.
>> - "id:" links to headings in external files are exported as ID value
>> with "ID-" prefix. These links are *broken* currently.
> Thanks a lot.
> Perfectly functional org-id links between two files are broken when published
> to HTML.
> I suppose a bug should be opened about that?
> (I can do that in a few weeks.)

It is already tracked on https://updates.orgmode.org/ as
"Inconsistent handling of id: links to other file during publish"

  reply	other threads:[~2021-09-20 14:39 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-08-13 22:28 org-id with ox-html inkbottle
2021-08-14  0:50 ` inkbottle
2021-08-14  4:20   ` inkbottle
2021-08-17  3:11     ` Internal link broken when publishing (was org-id with ox-html) inkbottle
2021-08-22 20:42       ` inkbottle
2021-08-24 15:23         ` Maxim Nikulin
2021-09-07 15:46           ` chris
2021-09-14 16:33             ` Max Nikulin
2021-09-20  0:05               ` chris
2021-09-20 14:13                 ` Max Nikulin [this message]
2021-09-20 15:26                   ` chris

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:

  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='sia4u6$10ll$1@ciao.gmane.io' \
    --to=manikulin@gmail.com \
    --cc=emacs-orgmode@gnu.org \


* 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


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).