emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Aaron Ecay <aaronecay@gmail.com>
To: "T.F. Torrey" <tftorrey@tftorrey.com>, Rasmus <rasmus@gmx.us>
Cc: emacs-orgmode@gnu.org
Subject: Re: Bug: HTML export ignoring CUSTOM_ID properties
Date: Sat, 18 Apr 2015 23:38:28 +0100	[thread overview]
Message-ID: <87zj65jczm.fsf@gmail.com> (raw)
In-Reply-To: <877ft9cmyk.fsf@jack.tftorrey.com>

Hi Terry,

I don’t think it’s necessary to be combative.  Rasmus is doing his best,
as are all the org developers.  Sometimes things break by accident –
that is the nature of beta software.  The problems you raised are
important.  Let’s try to figure out how to fix them.

You wrote:

> Links may work from inside Org, but the original intent of CUSTOM_ID was
> to produce a stable ID for the HTML export that could be linked to from
> outside Org.

I think this is true.  Looking at the pages in Worg, for example,
provides ample evidence of this strategy in action.

CUSTOM_ID is also sometimes needed for latex export
(cf. org-latex-prefer-user-labels).  It is important for IDs to be
unique, and to conform to certain format restrictions.  What if
CUSTOM_ID properties were checked for these requirements when exporting,
raising an error if they are not suitable and otherwise passing through
to the export output?  This would maintain CUSTOM_ID as an interface to
labeling systems outside org (latex \ref{}, html #anchor links, ...),
but would also make export more robust.  It’s also in line with recent
changes to raise export errors for undefined macros, unresolvable links,
etc.

--
Aaron Ecay

  reply	other threads:[~2015-04-18 22:38 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-04-16 23:19 Bug: HTML export ignoring CUSTOM_ID properties T.F. Torrey
2015-04-17  0:20 ` Rasmus
2015-04-17 18:20   ` T.F. Torrey
2015-04-18 13:57     ` Rasmus
2015-04-18 18:26       ` T.F. Torrey
2015-04-18 22:38         ` Aaron Ecay [this message]
2015-04-19  3:40           ` T.F. Torrey
2015-04-18 23:08         ` Nicolas Goaziou
2015-04-19  4:20           ` T.F. Torrey
2015-04-19  9:08             ` Nicolas Goaziou
2015-04-19 21:11               ` T.F. Torrey
2015-04-19 14:47             ` Rasmus
2015-04-21  5:37       ` Daniel Clemente
2015-04-21  7:25         ` Nicolas Goaziou
2015-04-23 18:15           ` Daniel Clemente
2015-04-23 19:21             ` Nicolas Goaziou

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=87zj65jczm.fsf@gmail.com \
    --to=aaronecay@gmail.com \
    --cc=emacs-orgmode@gnu.org \
    --cc=rasmus@gmx.us \
    --cc=tftorrey@tftorrey.com \
    /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).