From: kadal <kadalcalypse@gmail.com>
To: emacs-orgmode@gnu.org
Subject: Re: ox-html export bug
Date: Fri, 8 Sep 2017 10:18:18 -0700 [thread overview]
Message-ID: <889ae077-40da-355b-9574-e9b73127910e@gmail.com> (raw)
In-Reply-To: <87bmmlwkzp.fsf@nicolasgoaziou.fr>
>> Fair point. Would it be sufficient to give these type of links a class,
>> say "org-internal-links". Then you should be able to explicitly turn off
>> the content for these links.
>>
>> .org-internal-links::after {content:"";}
I don't know, looks like a bug to me.
> I haven't put much thought into it, but I wonder if it would be possible
> to ignore EXTRA-IDS and only use PREFERRED-ID (see `org-html-headline'),
> i.e., use
>
> (or (org-element-property :CUSTOM_ID headline)
> (org-export-get-reference headline info))
>
> It could be a problem when publishing to HTML, but I'm not sure at this
> point.
Going back to the original report:
------------------------------
<div id="outline-container-orgf4e5527" class="outline-2">
<h2 id="orgf4e5527"><span class="section-number-2">1</span> heading 1</h2>
</div>
<div id="outline-container-orge4e91c4" class="outline-2">
<h2 id="my-name"><a id="orge4e91c4"></a><span
class="section-number-2">2</span> heading 2</h2>
<div class="outline-text-2" id="text-my-name">
</div>
-------------------------------
The first headline with no CUSTOM_ID exports to "<h2 id="orgf4e5527">"
The second headline with a CUSTOM_ID exports to "<h2 id="my-name"><a
id="orge4e91c4"></a>"
Seems like the second one should export to either "<h2 id="my-name">" or
"<h2 id="my-name" id="orge4e91c4">". Not sure why the empty link is
being inserted or needs to be there at all.
Deepak
next prev parent reply other threads:[~2017-09-08 17:18 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-07 17:02 ox-html export bug kadal
2017-09-07 17:32 ` Nicolas Goaziou
2017-09-07 18:04 ` kadal
2017-09-08 8:55 ` Rasmus
2017-09-08 10:19 ` Nicolas Goaziou
2017-09-08 17:18 ` kadal [this message]
2017-09-08 17:32 ` Nicolas Goaziou
2017-09-08 17:40 ` kadal
2017-09-08 18:52 ` Fabrice Popineau
2017-09-09 22:37 ` Nicolas Goaziou
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=889ae077-40da-355b-9574-e9b73127910e@gmail.com \
--to=kadalcalypse@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).