Links to id:xxxxxx don't work in exported html

Links to id:xxxxxx don't work in exported html

[Friedrich Delgado Friedrichs]

Hi!

I really like org-link-to-org-use-id, however it breaks links to
org items in html export for me.

I have the following test file:

** Test [[id:45c4a467-b6ee-497c-9ed7-40342738e1c2][Item in a different org-file]]
 - [[id:frz5htg0rhe0][Yet another item in a different org file]]

   [[id:8611fa8f-7460-47b6-8edd-67e1ec25c5ce][Local Item]]

** Local Item
   :PROPERTIES:
   :ID:       8611fa8f-7460-47b6-8edd-67e1ec25c5ce
   :END:

The two external links have the mentioned ids and the links work in org,
however html export gives me the following html snippet:

<div id="outline-container-1.1" class="outline-3">
<h3 id="sec-1.1">1.1 Test <i>&lt;id:45c4a467-b6ee-497c-9ed7-40342738e1c2&gt;</i> </h3>
<div id="text-1.1">

<ul>
<li>
<i>&lt;id:frz5htg0rhe0&gt;</i>

<p>
<a href="#sec-1.2">Local Item</a>
</p>
</li>
</ul>
</div>

</div>

<div id="outline-container-1.2" class="outline-3">
<h3 id="sec-1.2">1.2 Local Item </h3>
<div id="text-1.2">

</div>
</div>

i.e. only the internal link works, the links to different org files
are only displayed by their ids.


-- 
        Friedrich Delgado Friedrichs <friedel@nomaden.org>
                             TauPan on Ircnet and Freenode ;)

Re: Links to id:xxxxxx don't work in exported html

[Carsten Dominik]

Hi Friedrich,

thanks for bringing this up.  Yes, this should work.
Back when I did the id links, I thought it would be very hard,
but fortunately I did put the basic framework for additional
targets in place already a while ago, in response to a request
by Matt for hard targets that are good for permanent HTML links.

Now you can use the ID's.  The advantage is that, as you move
links around, they will continue to work.  So this is really
great for Notes that you might want to re-organize.

On the other hand, when building a website, explicit targets
may be more self-explanatory:

#<<hard-target>>
* Headline that should be linked to

HTH

- Carsten

On Jan 8, 2009, at 3:49 PM, Friedrich Delgado Friedrichs wrote:

> Hi!
>
> I really like org-link-to-org-use-id, however it breaks links to
> org items in html export for me.
>
> I have the following test file:
>
> ** Test [[id:45c4a467-b6ee-497c-9ed7-40342738e1c2][Item in a  
> different org-file]]
> - [[id:frz5htg0rhe0][Yet another item in a different org file]]
>
>   [[id:8611fa8f-7460-47b6-8edd-67e1ec25c5ce][Local Item]]
>
> ** Local Item
>   :PROPERTIES:
>   :ID:       8611fa8f-7460-47b6-8edd-67e1ec25c5ce
>   :END:
>
> The two external links have the mentioned ids and the links work in  
> org,
> however html export gives me the following html snippet:
>
> <div id="outline-container-1.1" class="outline-3">
> <h3 id="sec-1.1">1.1 Test <i>&lt;id:45c4a467- 
> b6ee-497c-9ed7-40342738e1c2&gt;</i> </h3>
> <div id="text-1.1">
>
> <ul>
> <li>
> <i>&lt;id:frz5htg0rhe0&gt;</i>
>
> <p>
> <a href="#sec-1.2">Local Item</a>
> </p>
> </li>
> </ul>
> </div>
>
> </div>
>
> <div id="outline-container-1.2" class="outline-3">
> <h3 id="sec-1.2">1.2 Local Item </h3>
> <div id="text-1.2">
>
> </div>
> </div>
>
> i.e. only the internal link works, the links to different org files
> are only displayed by their ids.
>
>
> -- 
>        Friedrich Delgado Friedrichs <friedel@nomaden.org>
>                             TauPan on Ircnet and Freenode ;)
>
>
> _______________________________________________
> Emacs-orgmode mailing list
> Remember: use `Reply All' to send replies to the list.
> Emacs-orgmode@gnu.org
> http://lists.gnu.org/mailman/listinfo/emacs-orgmode

Re: Links to id:xxxxxx don't work in exported html

[Friedrich Delgado Friedrichs]

Hm...

Carsten Dominik schrieb:
> Now you can use the ID's.  The advantage is that, as you move
> links around, they will continue to work.  So this is really
> great for Notes that you might want to re-organize.
---Zitatende---

I can't get this to work.

My config is

org-publish-project-alist: 
(("all" :auto-index t :base-directory "~/git/Org/" :publishing-directory "~/opt/Org-Publish" :recursive t)
 ("common" :auto-index t :base-directory "~/git/Org/" :publishing-directory "~/opt/Org-Publish")
 ("work-only" :auto-index t :base-directory "~/git/Org/work" :publishing-directory "~/opt/Org-Publish/work")
 ("home" :auto-index t :base-directory "~/git/Org/home" :publishing-directory "~/opt/Org-Publish/home")
 ("work" :components
  ("common" "work-only")))

I published with "all" and the snippet I posted before results in:

<div id="outline-container-1.1" class="outline-3">
<h3 id="sec-1.1">1.1 Test <a href="../opt/Org-Publish/Collect.html#45c4a467-b6ee-497c-9ed7-40342738e1c2">Item in a different org-file</a></h3>
<div id="text-1.1">

<ul>
<li>
<a href="../opt/Org-Publish/Collect.html#frz5htg0rhe0">Yet another item in a different org file</a>

<p>
<a href="#sec-1.2">Local Item</a>

</p>
</li>
</ul>
</div>

</div>

<div id="outline-container-1.2" class="outline-3">
<h3 id="sec-1.2"><a name="8611fa8f-7460-47b6-8edd-67e1ec25c5ce" id="8611fa8f-7460-47b6-8edd-67e1ec25c5ce"></a>1.2 Local Item </h3>
<div id="text-1.2">

</div>
</div>

</div>

<div id="outline-container-2" class="outline-2">
<h2 id="sec-2">2 Notes </h2>
<div id="text-2">




</div>

</div>

The published file is Collect.org, and the links point to Collect.html, however they reside
in different files (the first is in work/Sonstiges.org and the other one is in Common.org).

And I get relative links, even though I configured absolute directories.

However work/Sonstiges.html and Common.html contain the correct anchors.

Should I post a complete set of files for reproducing the problem?

-- 
        Friedrich Delgado Friedrichs <friedel@nomaden.org>
                             TauPan on Ircnet and Freenode ;)

Re: Links to id:xxxxxx don't work in exported html

[Carsten Dominik]

Hi Friedrich,

first of all, Org does expect that the file containing
the link and the file containing the target have the same
relative path both in the staging area (where the .org files are)
and in the publishing area (where the .html files will be).  I don't
know how else to approach this.

Second, if I understand correctly, the your links are located
in "Collect.org", and the targets are in different files.

This means that Org is confused about what files contain
which anchors.  The relation between files and anchors is stored in  
the file
~/.emacs.d/org-id-locations.  It can be updated with

  M-x org-id-update-id-locations

This list may come out of sync if you move entries
from one file to another not using Org commands, but,
for example, cut and paste with the mouse.

Can you please check if updating helps?  If not, can you
take a look at the file org-id-locations and see what it has
to say about the id's you are checking?


If all this does not help, please make me a complete test
case and I will try to reproduce it with that.

- Carsten

On Jan 9, 2009, at 2:50 PM, Friedrich Delgado Friedrichs wrote:

> Hm...
>
> Carsten Dominik schrieb:
>> Now you can use the ID's.  The advantage is that, as you move
>> links around, they will continue to work.  So this is really
>> great for Notes that you might want to re-organize.
> ---Zitatende---
>
> I can't get this to work.
>
> My config is
>
> org-publish-project-alist:
> (("all" :auto-index t :base-directory "~/git/Org/" :publishing- 
> directory "~/opt/Org-Publish" :recursive t)
> ("common" :auto-index t :base-directory "~/git/Org/" :publishing- 
> directory "~/opt/Org-Publish")
> ("work-only" :auto-index t :base-directory "~/git/Org/ 
> work" :publishing-directory "~/opt/Org-Publish/work")
> ("home" :auto-index t :base-directory "~/git/Org/home" :publishing- 
> directory "~/opt/Org-Publish/home")
> ("work" :components
>  ("common" "work-only")))
>
> I published with "all" and the snippet I posted before results in:
>
> <div id="outline-container-1.1" class="outline-3">
> <h3 id="sec-1.1">1.1 Test <a href="../opt/Org-Publish/ 
> Collect.html#45c4a467-b6ee-497c-9ed7-40342738e1c2">Item in a  
> different org-file</a></h3>
> <div id="text-1.1">
>
> <ul>
> <li>
> <a href="../opt/Org-Publish/Collect.html#frz5htg0rhe0">Yet another  
> item in a different org file</a>
>
> <p>
> <a href="#sec-1.2">Local Item</a>
>
> </p>
> </li>
> </ul>
> </div>
>
> </div>
>
> <div id="outline-container-1.2" class="outline-3">
> <h3 id="sec-1.2"><a name="8611fa8f-7460-47b6-8edd-67e1ec25c5ce"  
> id="8611fa8f-7460-47b6-8edd-67e1ec25c5ce"></a>1.2 Local Item </h3>
> <div id="text-1.2">
>
> </div>
> </div>
>
> </div>
>
> <div id="outline-container-2" class="outline-2">
> <h2 id="sec-2">2 Notes </h2>
> <div id="text-2">
>
>
>
>
> </div>
>
> </div>
>
> The published file is Collect.org, and the links point to  
> Collect.html, however they reside
> in different files (the first is in work/Sonstiges.org and the other  
> one is in Common.org).
>
> And I get relative links, even though I configured absolute  
> directories.
>
> However work/Sonstiges.html and Common.html contain the correct  
> anchors.
>
> Should I post a complete set of files for reproducing the problem?
>
> -- 
>        Friedrich Delgado Friedrichs <friedel@nomaden.org>
>                             TauPan on Ircnet and Freenode ;)
>
>
> _______________________________________________
> Emacs-orgmode mailing list
> Remember: use `Reply All' to send replies to the list.
> Emacs-orgmode@gnu.org
> http://lists.gnu.org/mailman/listinfo/emacs-orgmode

Re: Links to id:xxxxxx don't work in exported html

[Friedrich Delgado Friedrichs]

Hiho!

Carsten Dominik schrieb:
> first of all, Org does expect that the file containing
> the link and the file containing the target have the same
> relative path both in the staging area (where the .org files are)
> and in the publishing area (where the .html files will be).  I don't
> know how else to approach this.

I read that in the git log, and interpreted it as:

git/Org/Collect.org -> git/Org/work/Sonstiges.org
opt/Org-Publish/Collect.html opt/Org-Publish/work/Sonstiges.html

same relative path ./ -> work
or the other way round it's . -> ../

Now it seems like you might mean they have to be in the same path.

So I've tried setting the publishing directory to git/Org.

Is that necessary? Or was my first understanding correct?

> This means that Org is confused about what files contain
> which anchors.  The relation between files and anchors is stored in the 
> file
> ~/.emacs.d/org-id-locations.  It can be updated with
>
>  M-x org-id-update-id-locations
--Zitatende---

Ok, after calling that command, most of the links work correctly
(except for a few pathological cases, which occur when the
link-description contains a link).

Many thanks! :)
-- 
        Friedrich Delgado Friedrichs <friedel@nomaden.org>
                             TauPan on Ircnet and Freenode ;)

Re: Links to id:xxxxxx don't work in exported html

[Carsten Dominik]

On Jan 9, 2009, at 5:59 PM, Friedrich Delgado Friedrichs wrote:

> Hiho!
>
> Carsten Dominik schrieb:
>> first of all, Org does expect that the file containing
>> the link and the file containing the target have the same
>> relative path both in the staging area (where the .org files are)
>> and in the publishing area (where the .html files will be).  I don't
>> know how else to approach this.
>
> I read that in the git log, and interpreted it as:
>
> git/Org/Collect.org -> git/Org/work/Sonstiges.org
> opt/Org-Publish/Collect.html opt/Org-Publish/work/Sonstiges.html
>
> same relative path ./ -> work
> or the other way round it's . -> ../


This is exactly what I meant, and how it works in my own test case  
here....

>
>
> Now it seems like you might mean they have to be in the same path.
>
> So I've tried setting the publishing directory to git/Org.
>
> Is that necessary? Or was my first understanding correct?
>
>> This means that Org is confused about what files contain
>> which anchors.  The relation between files and anchors is stored in  
>> the
>> file
>> ~/.emacs.d/org-id-locations.  It can be updated with
>>
>> M-x org-id-update-id-locations
> --Zitatende---
>
> Ok, after calling that command, most of the links work correctly
> (except for a few pathological cases, which occur when the
> link-description contains a link).
>
> Many thanks! :)
> -- 
>        Friedrich Delgado Friedrichs <friedel@nomaden.org>
>                             TauPan on Ircnet and Freenode ;)
>
>
> _______________________________________________
> Emacs-orgmode mailing list
> Remember: use `Reply All' to send replies to the list.
> Emacs-orgmode@gnu.org
> http://lists.gnu.org/mailman/listinfo/emacs-orgmode

Re: Links to id:xxxxxx don't work in exported html

[Friedrich Delgado Friedrichs]

Hiho

Carsten Dominik schrieb:
> On Jan 9, 2009, at 5:59 PM, Friedrich Delgado Friedrichs wrote:
>> same relative path ./ -> work
>> or the other way round it's . -> ../
> This is exactly what I meant, and how it works in my own test case  
> here....
--Zitatende---

Ok, works here too.  The id locations were outdated for some reason.



-- 
        Friedrich Delgado Friedrichs <friedel@nomaden.org>
                             TauPan on Ircnet and Freenode ;)

Re: Links to id:xxxxxx don't work in exported html

[Carsten Dominik]

On Jan 12, 2009, at 5:09 PM, Friedrich Delgado Friedrichs wrote:

> Hiho
>
> Carsten Dominik schrieb:
>> On Jan 9, 2009, at 5:59 PM, Friedrich Delgado Friedrichs wrote:
>>> same relative path ./ -> work
>>> or the other way round it's . -> ../
>> This is exactly what I meant, and how it works in my own test case
>> here....
> --Zitatende---
>
> Ok, works here too.  The id locations were outdated for some reason.

Good to hear.  I guess I need to make a more prominent notice
about the need to occasionally update these.

When you follow an ID link and the entry can not be found in the target
file, then an update happens automatically.

- Carsten

Re: Links to id:xxxxxx don't work in exported html

[Tom Breton (Tehom)]

> Message: 4
> Date: Thu, 8 Jan 2009 15:49:16 +0100
> From: Friedrich Delgado Friedrichs <friedel@nomaden.org>
> Subject: [Orgmode] Links to id:xxxxxx don't work in exported html
> To: Emacs-orgmode mailing list <emacs-orgmode@gnu.org>
> Message-ID: <20090108144916.GB5649@taupan.ath.cx>
> Content-Type: text/plain; charset=us-ascii
>
> Hi!
>
> I really like org-link-to-org-use-id, however it breaks links to
> org items in html export for me.
>
> I have the following test file:
>
> ** Test [[id:45c4a467-b6ee-497c-9ed7-40342738e1c2][Item in a different
> org-file]]
[snip]
>
> The two external links have the mentioned ids and the links work in org,
> however html export gives me the following html snippet:
>
> <div id="outline-container-1.1" class="outline-3">

Looks like the problem is that it is html-escaped because it's the headline.
I actually think this is the right behavior.

Tom Breton (Tehom)