EPUB export of headings with automatic numbering ignores heading levels and makes them a list

[athelas64]

If you use automatic numbering for your chapters (including multi-level), even though you have defined in export tagging and proper H levels in Style settings for HTML/EPUB, these are completely ignored.

All headings are exported as <ol> <li> elements.

If I convert automatic numbering into text, chapter headings are correctly exported according to their export settings as various H levels and proper semantics is preserved.

According to HTML specification, lists can contain headings, so this seems to be bug. I don't think I will live long enough for this one to be fixed, so in the meantime, I would like to ask for some work-arounds.

One is to convert all headings from automatic numbering to text, but this has to be done one-by-one in a backwards fasion. Are you aware of a script that could do this - just for a particular set of styles? - I don't want all lists in the document to be converted into text because of accessibility complaince - just the headings.

Thank you very much for your insights!

[James Gifford—NitroPress]

This is a new one. I can't think of it coming up before. Will be experimenting to see where it falls on the structure/standards/bug spectrum. I can see where the collision would come from, though.

[James Gifford—NitroPress]

I am not seeing any problem.

I took one of my simple test docs and added five headings with auto numbering. They're fine in the text and generate a TOC that accurately reflects them, numbering and all.

Yes, each heading is wrapped in an <ol><lI> structure. But this does not appear to affect any part of function and the slight format variation can be corrected.

What do you see as the problem, here?

You can eliminate the problem and have the Headings converted to plain text by selecting Text | Lists | Numbers: Convert to Text in the export menu. Does that solve the issue for you?

I don't know if this is a change  — quite a few things were adjusted with v19.2 and later to accommodate the accessibility features — but I can't see it as a bug.