Incremental IDs plugin

[Doitsu]

Originally Posted by democrite

Would you consider some way to id some set of tags hierarchically?

Somehow, I fail to see the benefit of hierarchical ids. What exactly would you use them for?

[democrite]

Main use at the moment is I would like to create the XHTML TOC such that the link for sections is merely the number like 1, 1.1, etc. with text not as part of the anchor tag. For very long works with many sections, I can then add annotations or highlights for important sections. Helps keep track of important sections of interest in long works.

[DiapDealer]

You're not talking about the anchor tag's id attributes being only numbers are you?

[democrite]

If ids were as sec1, sec1.1, sec1.1a etc. where I could specify a range of header tags to process e.g. H2 to H4 then after generating the XHTML TOC I could use regex to style sections like:

<a href=“./file.xhtml#sec1.1”>1.1</a> Section title</a>

I often tend to study academic or scientific works where there could be 50-100+ sections and coding as such would more easily allow annotations or highlights within the toc so I can keep track of notable sections.

[phillipgessert]

Perhaps you could do that with CSS counters. They aren't universally supported AFAIK, but I don't guess that matters so long as they're supported by whatever device you're using.

[Doitsu]

Originally Posted by democrite

If ids were as sec1, sec1.1, sec1.1a etc. where I could specify a range of header tags to process e.g. H2 to H4 then after generating the XHTML [...]

Since you can enter any id prefix that you want, you could simply process all h2-h4 tags and enter sec1, sec1. etc. as the id prefix.

[democrite]

Maybe I’m missing something but not sure how that’d work. E.g. H3+ after the first H2 numbered sec1.1 1.2 1.2.1 1.2.1 1.3 etc. then next set after second H2 sec 2.1 2.1.1 etc.

I’m ok with CSS counters but not sure how I’d code the links such that they’d include the number and header text would be outside. Maybe possible but haven’t found it yet.

[phillipgessert]

I would try first pulling the title text out of the <a> tags via regex, leaving you with static text following an unlabeled link, then add the counter via a::before.

<a href='#target'></a>My Informative Title

a::before {
  content: counter(heading) '.' counter(subheading)  ': ';
}

Might be a start, anyway.

[Doitsu]

Originally Posted by democrite

Maybe I’m missing something but not sure how that’d work. E.g. H3+ after the first H2 numbered sec1.1 1.2 1.2.1 1.2.1 1.3 etc. then next set after second H2 sec 2.1 2.1.1 etc.

You're right, you couldn't do this with the Incremental IDs plugin. You'll have to modify the plugin yourself to add that functionality.

Originally Posted by phillipgessert

I would try first pulling the title text out of the <a> tags via regex, leaving you with static text following an unlabeled link, then add the counter via a::before.

Unfortunately, many e-readers and epub apps don't support CSS counters.
I've created a proof-of-concept epub3 book with CSS counters based on a StackOverflow post that you could use for testing.
(CSS counters work in KF8 and KFX books, however, according to the Amazon Kindle Publishing Guidelines, you can't use them in Kindle books.)

[1v4n0]

I used this plugin to interlink between sections of two xhtml files in an epub, then I split the files with sigil's split marker, and it didn't update the links to the new names of the xhtml files. Don't know whether this is an issue with Sigil or with the Plugin. I'm using an old version of sigil, the last one with "book view".

Anyway awesome job

[KevinH]

Working links are updated (href, src, etc) but ids are not changed as they must be unique strings in any one file so splitting them will not impact that uniqueness.

[Doitsu]

Originally Posted by 1v4n0

I used this plugin to interlink between sections of two xhtml files in an epub, then I split the files with sigil's split marker, and it didn't update the links to the new names of the xhtml files.

As KevinH has already pointed out, Split at Markers will only update working links.
Please validate your epub book with my EpubCheck plugin before and after using the AddIDs plugin. (You can also check links in your book with Tools > Reports > Links.)
If either tool reports broken links after using the AddIDs plugin, you most likely didn't use the plugin correctly.