Hmmm ---- this seems so deliberate...  For bbdb links this even seems to
make sense...  But how could I avoid this "footnote like" behaviour?



  Sebastian


>>
>>
>> HTML export works as expected.
>>
>>
>> Example Org file:
>>
>>  --8<---------------cut here---------------start------------->8--
>>
>> * Test links
>>
>>  [[track:((9.707032442092896 52.37033874553582) (9.711474180221558 52.375238282987))FILENAME.svg][DESCRIPTION]]
>>
>>  --8<---------------cut here---------------end--------------->8--
>>
>>
>>
>>
>> Results in ASCII (just the section with the link):
>>
>>  --8<---------------cut here---------------start------------->8--
>>
>> 1 Test links
>> ~~~~~~~~~~~~~
>>
>>  [DESCRIPTION]
>>
>>  [DESCRIPTION]: track:((9.707032442092896 52.37033874553582) (9.711474180221558 52.375238282987))FILENAME.svg
>>
>>
>>  --8<---------------cut here---------------end--------------->8--
>>
>>
>>
>> HTML works:
>>
>>  --8<---------------cut here---------------start------------->8--
>>
>> <div id="outline-container-1" class="outline-2">
>> <h2 id="sec-1"><span class="section-number-2">1</span> Test links </h2>
>> <div class="outline-text-2" id="text-1">
>>
>>
>> <p>
>> <a href="FILENAME.svg">DESCRIPTION</a>
>> </p></div>
>> </div>
>> ...
>>  --8<---------------cut here---------------end--------------->8--
>>
>>
>>
>>
>> Now as write this, I found I could as well use a bbdb link and come to
>> similar results...
>>
>> :-(
>>
>>
>>  Sebastian
>>