Re: Re: unique id=-values in aggregated html-exported docs

[Dirk-Jan C. Binnema <djcb.bulk@gmail.com>]

Hi,

>>>>> On Wed, 12 May 2010 19:02:42 +0200, Sebastian Rose ("SR") wrote:


  SR> Can you verify, that those are clashing IDs?
  >> 
  >> Sure:
  >> 
  >> 
  >> % cat index.html | grep id=
  >> [....]
  >> 
  >> <div id="outline-container-1" class="outline-3">
  >> <h3 id="sec-1">
  >> <div class="outline-text-3" id="text-1">
  >> <div id="outline-container-1" class="outline-3">

  SR> Funny - cannot verify that and never saw it. Why are your section
  SR> numbers not increased?

  SR> Could you please provide a simple testfile?

Well, the issue is about *aggregated* html files; so
      test1.org => test1.html, and
      test2.org => test2.html
in both test1.html and test2.html, the ids will be unique; the problem occurs
when we aggregate (concatenate) test1.html and test2.html into a big html
file; this is e.g. what happens when creating a blog, and your putting
together the last n posts. Then, the ids in the aggregated document will not
be unique.
  

  >> So, the issue is with aggregating separate exported html blobs into one
  >> page; of course org-mode has no real control over the uniqueness of the
  >> ids then.
  >> 
  >> My idea would be that we could add some per-exported org-file cookie, so
  >> the ids could be something like:
  >> 
  >> id="text-456EF-1"

  SR> How to refer to a certain section in a stylesheet then?

For aggregated documents that does not really work when using ids; instead,
classes are to be used for that. I mean, with aggregated documents there may
be multiple text-1 and (worse) multiple footnotes.

I'm not sure, why would one want to use ids in this case, and not classes?


  SR> A quick fix would be to just add `summary=""' to the table definition:
  >> 
  SR> <table summary="" ...>
  >> 
  >> Well, it's easy to shut up the html-validators (like tidy), but for true
  >> accessibility it'd be nice to set the summary to something meaningful
  >> (same for the alt= attribute of images). Not sure if that is a priority
  >> right now, and I guess it might add some complexity.

  SR> Agreed. But Org cannot guess.

Indeed; I have no idea how hard it would be to add e.g,.

  #+summary: table of foo per capita
(which could also be use for the alt= is in html image export)

org-babel already has #+tblname; maybe that could be extended?
  
Best wishes,
Dirk.

-- 
Dirk-Jan C. Binnema                  Helsinki, Finland
e:djcb@djcbsoftware.nl           w:www.djcbsoftware.nl
pgp: D09C E664 897D 7D39 5047 A178 E96A C7A1 017D DA3C