emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: mdl@imapmail.org
To: Carsten Dominik <dominik@science.uva.nl>
Cc: emacs-orgmode@gnu.org
Subject: Re: Anchors/targets in org-export/publish
Date: Mon, 17 Nov 2008 14:52:23 -0600	[thread overview]
Message-ID: <87y6zi13eg.fsf@fastmail.fm> (raw)
In-Reply-To: <570FDFE9-C3C9-4E77-8B04-64DAA7B6F33E@uva.nl> (Carsten Dominik's message of "Sun\, 16 Nov 2008 22\:27\:57 +0100")

Carsten Dominik <dominik@science.uva.nl> writes:

> On Nov 13, 2008, at 5:36 PM, Matthew Lundin wrote:
>
>>
>> Question about org-export:
>>
>> I'd like to create invisible radio targets to html anchor links using
>> org-export.
>>
>> E.g.,
>>
>> # <<radiotarget>>
>>
>> should become
>>
>> <a name="radiotarget"></a>
>>
>> Currently, however, there are a couple of behaviors of org-exp.el that
>> make this difficult.
>>
>> 1) Org-export does convert invisible targets, but it puts paragraph
>> tags around the anchor, thus creating an empty line in the html
>> export, which messes up the layout.
>>
>>         <p>
>>         <a name="radiotarget">&nbsp;</a>
>>         </p>
>
> This actually only happens if you surround the anchor by empty
> lines.  Put it directly before a paragraph, or inside one, and
> this will not happen.
>
>> 2) If the commented radio target is directly beneath or above a
>> headline, it is not exported. I checked org-exp.el and this seems to
>> be an intentional behavior. I'm not sure I understand the reasons
>> behind this, as it prevents one from giving custom anchors to
>> headlines.
>>
>> This is especially important if one wants to be able to create
>> permalinks to headlines from other pages.
>
> This is now fixed, the invisible targets are added as empty anchors
> to the headline that must be directly before or after the anchor.
>
>
>
> On Nov 13, 2008, at 6:18 PM, Matthew Lundin wrote:
>>>
>>>         <p>
>>>         <a name="radiotarget">&nbsp;</a>
>>>         </p>
>>
>> Quick follow up to my previous message. Would it be possible to remove
>> the &nbsp above. That would prevent an extra line in the output, but
>> it might render the link useless in some browsers.
>
> Fixed as well, thanks.  I guess when I implemented this a long time
> ago, I did not realize that empty anchors are allowed.
>
>> (I should also apologize for the strong phrase "messes up."
>
> Don't worry, no offense taken.
>
> - Carsten

Didn't see the fix before I sent my last message.

Thanks so much! This is fantastic.

- Matt

      reply	other threads:[~2008-11-17 20:52 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-11-13 16:36 Anchors/targets in org-export/publish Matthew Lundin
2008-11-13 17:18 ` Matthew Lundin
2008-11-16 20:29 ` Carsten Dominik
2008-11-17 20:49   ` mdl
2008-11-16 21:27 ` Carsten Dominik
2008-11-17 20:52   ` mdl [this message]

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=87y6zi13eg.fsf@fastmail.fm \
    --to=mdl@imapmail.org \
    --cc=dominik@science.uva.nl \
    --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).