From: Nicolas Goaziou <mail@nicolasgoaziou.fr>
To: "T.F. Torrey" <tftorrey@tftorrey.com>
Cc: emacs-orgmode@gnu.org, Rasmus <rasmus@gmx.us>
Subject: Re: Bug: HTML export ignoring CUSTOM_ID properties
Date: Sun, 19 Apr 2015 01:08:57 +0200 [thread overview]
Message-ID: <87egnhm3ue.fsf@nicolasgoaziou.fr> (raw)
In-Reply-To: <877ft9cmyk.fsf@jack.tftorrey.com> (T. F. Torrey's message of "Sat, 18 Apr 2015 11:26:11 -0700")
Hello,
tftorrey@tftorrey.com (T.F. Torrey) writes:
> 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. With the changed functionality, all existing links to
> presidents.html#clinton are broken, because the usage of CUSTOM_ID has
> changed. Any custom CSS is also broken, for the same reason.
>
> With the new usage, CUSTOM_ID and ID have virtually the same
> functionality.
Good point.
> The code on master is *supposed* to work as advertised. It identifies
> itself as 8.3 beta. Changes that break functionality in exploratory
> ways are alpha changes.
"beta" is indeed misleading. I suggest to ignore it.
As Rasmus pointed out, master is where development happens. Some changes
introduced here may break Org. If one such change makes Org unusable for
you, you can easily revert Org to an earlier, working, commit, without
fuss. Of course, we appreciate if you report the problem encountered
beforehand.
> Ha ha. There are many tools capable of exporting plain-text documents
> to HTML with predictable and stable ID's.
Considering that not any string is eligible as HTML id (e.g., forbidden
characters), either these tools are putting restrictions on chosen IDs
or they are lying.
> As you said, they aren't your changes and it isn't your decision.
I overlooked the problem in HTML and made a mistake. It happens, more
often than I would like. However, you are not required to be obnoxious
about it. It helps no one.
The problem should be fixed in 0449b785b4b58ec16e1aac126634de70eee519a4.
Thank you for reporting it.
Regards,
--
Nicolas Goaziou
next prev parent reply other threads:[~2015-04-18 23:07 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
2015-04-19 3:40 ` T.F. Torrey
2015-04-18 23:08 ` Nicolas Goaziou [this message]
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=87egnhm3ue.fsf@nicolasgoaziou.fr \
--to=mail@nicolasgoaziou.fr \
--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).