From: Jambunathan K <kjambunathan@gmail.com>
To: emacs-orgmode@gnu.org
Subject: Broken CUSTOMID links
Date: Fri, 05 Nov 2010 23:23:58 +0530 [thread overview]
Message-ID: <81mxpnwtah.fsf@gmail.com> (raw)
Note the 'H:1' in options line. Export this to HTML. Note that CUSTOMID
link is broken. A snippet of relevant HTML section is attached
below.
Change 'H:1' to 'H:3' note that there is no more brokenness.
Possible root cause: When headlines are turned to list 'extra-targets'
are not identified correctly.
(This bug is unrelated to any of the previous internal link bugs that I
have reported)
# Input file
#+OPTIONS: H:1
* Links
** Targets
*** Fuzzy Target
*** Target with CUSTOMID
:PROPERTIES:
:CUSTOM_ID: aabbccddeeff
:END:
*** Dedicated Target
# <<Dedicated Target>>
*** <<<Radioed Target>>>
** References
*** References to Fuzzy Target
This is a link to [[Fuzzy Target]].
*** References to CUSTOMID links
This link to [[#aabbccddeeff][CUSTOMID Target]] is broken.
*** References to Dedicated Target
There is a link to nodesc [[Dedicated Target]] here. There is a link
to [[Dedicated%20Target][Jump to Dedicated Target]] here.
*** References to Radioed Links
This section has references to Radioed Target. One more reference
to Radioed Target.
#+begin_src html
<!-- Headline defined here -->
<ul>
<li id="sec-1_1_2">
<a name="sec-1_1_2" id="sec-1_1_2">
</a>
Target with CUSTOMID
<br/>
</li>
</ul>
<!-- Headline referenced here -->
<ul>
<li id="sec-1_2_2">
References to CUSTOMID links
<br/>
This link to
<a href="#aabbccddeeff">
CUSTOMID Target
</a>
is broken.
</li>
</ul>
#+end_src
Jambunathan K.
next reply other threads:[~2010-11-05 17:54 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-05 17:53 Jambunathan K [this message]
2010-11-06 19:36 ` Broken CUSTOMID links Carsten Dominik
2010-11-08 13:39 ` [PATCH 2/2] Fix broken CUSTOM_ID links Jambunathan K
2010-11-12 15:50 ` Carsten Dominik
2010-11-17 13:26 ` Carsten Dominik
2010-11-17 15:22 ` [PATCH: RESUBMITTED] " Jambunathan K
2010-11-21 8:45 ` Carsten Dominik
2010-11-17 15:22 ` Jambunathan K
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=81mxpnwtah.fsf@gmail.com \
--to=kjambunathan@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).