[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Orgmode] Anchors/targets in org-export/publish
From: |
mdl |
Subject: |
Re: [Orgmode] Anchors/targets in org-export/publish |
Date: |
Mon, 17 Nov 2008 14:52:23 -0600 |
User-agent: |
Gnus/5.11 (Gnus v5.11) Emacs/22.1 (gnu/linux) |
Carsten Dominik <address@hidden> 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"> </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"> </a>
>>> </p>
>>
>> Quick follow up to my previous message. Would it be possible to remove
>> the   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