From: Friedrich Delgado Friedrichs <friedel@nomaden.org>
To: Emacs-orgmode mailing list <emacs-orgmode@gnu.org>
Subject: Re: Links to id:xxxxxx don't work in exported html
Date: Fri, 9 Jan 2009 14:50:12 +0100 [thread overview]
Message-ID: <20090109135012.GA29016@taupan.ath.cx> (raw)
In-Reply-To: <F7A3A61E-D159-473C-8F3A-3C1FC422FF79@uva.nl>
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 ;)
next prev parent reply other threads:[~2009-01-09 13:50 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-08 14:49 Links to id:xxxxxx don't work in exported html Friedrich Delgado Friedrichs
2009-01-08 21:43 ` Carsten Dominik
2009-01-09 13:50 ` Friedrich Delgado Friedrichs [this message]
2009-01-09 15:21 ` Carsten Dominik
2009-01-09 16:59 ` Friedrich Delgado Friedrichs
2009-01-09 17:39 ` Carsten Dominik
2009-01-12 16:09 ` Friedrich Delgado Friedrichs
2009-01-13 9:17 ` Carsten Dominik
[not found] <20090108160642.23D3D29407@mail1.panix.com>
2009-01-08 23:07 ` Tom Breton (Tehom)
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=20090109135012.GA29016@taupan.ath.cx \
--to=friedel@nomaden.org \
--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).