emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Sebastian Rose <sebastian_rose@gmx.de>
To: Bernt Hansen <bernt@norang.ca>
Cc: org-mode mailing list <emacs-orgmode@gnu.org>
Subject: Re: Re: Custom entry IDs in HTML export
Date: Fri, 27 Mar 2009 22:32:58 +0100	[thread overview]
Message-ID: <87y6uqwsjw.fsf@kassiopeya.MSHEIMNETZ> (raw)
In-Reply-To: 87eiwiluft.fsf@gollum.intra.norang.ca

I don't think this is an important change.

Here some thoughts that come to mind in this context.

What we have now, just as Carstens said:

  # <<human-readable>>
  * Section B

Creates this headline in HTML:

  <h2 id="sec-2"><a name="human-readable" id="human-readable"></a>2 Section B </h2>

This is enough for all the use cases I can think of.

The section and headline may be detected through the anchor by any DOM
parser. Also, creating Org-files from Database entries or similar is
simple (Php):

fputs($fh, '
# <<id' . $row['id'] . '>>
* ' . $row['headline']);

If a change should be done, how will that change look like?

* Distinguishing automatic and human readable IDs

  One thing I like is, that we now _can_ distinguish the
  `human-readable-target' (human readable) from the `sec-2' (not human
  readable and not context related) using a regular expression.

  In org-info.js, I can now prefere the human readable ID in <a> from an
  automatic created one, and thus use that to create the links for `l'
  and `L'. The same holds true for other programming languages and

  If we open the <h3>'s ID for user defined values (bad), we can not
  distinguish those ID's using a regular expression and there is no way
  to detect the human readable one. There will be no way to _know_ that
  the <a>'s ID is the prefered one used for human readable links.

  If such a change should be done, I'd always prefer the (eventually
  existing) anchors ID for creating links.

  Conventions are not a bad thing in general, but they can lead to lot's
  of `if you...  else if... else...' in code and docs.

* Quality assurance

  The automatic IDs in the headline elements, and only those ID's,
  guaranty the functionality of export and cross referencing in an idiot
  proof way, which is what I prefer.



Sebastian Rose, EMMA STIL - mediendesign, Niemeyerstr.6, 30449 Hannover
Tel.:  +49 (0)511 - 36 58 472
Fax:   +49 (0)1805 - 233633 - 11044
mobil: +49 (0)173 - 83 93 417
Http:  www.emma-stil.de

  reply	other threads:[~2009-03-27 21:40 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-03-27 12:47 Custom entry IDs in HTML export Daniel Clemente
2009-03-27 16:16 ` Carsten Dominik
2009-03-27 17:57   ` Bernt Hansen
2009-03-27 21:32     ` Sebastian Rose [this message]
2009-03-30 11:49       ` Daniel Clemente
2009-04-16  6:55         ` Carsten Dominik
2009-04-16  8:50           ` Sebastian Rose
2009-04-16 11:28             ` Carsten Dominik
2009-04-16 13:14               ` Sebastian Rose
2009-04-16 17:14                 ` Carsten Dominik
2009-04-16 20:50                   ` Sebastian Rose
2009-04-16 21:26                     ` Carsten Dominik
2009-04-16 22:37                       ` Sebastian Rose
2009-04-17  4:11                         ` Carsten Dominik

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:

  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=87y6uqwsjw.fsf@kassiopeya.MSHEIMNETZ \
    --to=sebastian_rose@gmx.de \
    --cc=bernt@norang.ca \
    --cc=emacs-orgmode@gnu.org \


* 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


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).