Louise P. wrote:
Do you already have an idea whether the new functionality to convert index
entries in DOCX marking a page range will be implemented in v1.6 or v1.7 of w2x?
Almost certainly v1.6, but the feature you want (indexed terms which
point to ranges) will not be available before months as v1.5.1 was
released on August 31, 2018.
Also, for our further workflow, we would like to know what our DocBook-xml
shall look like once the page range functionality is possible in w2x. I see in
the DocBook specifications
(https://tdg.docbook.org/tdg/5.0/indexterm.singular.html) that there are two
ways to identify a range of text in DocBook:
"- Place an indexterm at the beginning of the range with class set to
startofrange and give this term an xml:id. Place another indexterm at the end of the
range with startref pointing to the xml:id of the starting indexterm. This second
indexterm must be empty.
Let's call this (A).
- Place the indexterm anywhere you like and point to the element that contains the
range of text you wish to index with the zone attribute on the indexterm. Note that
zone is defined as IDREFS, so a single indexterm can point to multiple ranges."
Let's call this (B).
I would say that a (human) DocBook author will tend to use more (A) than
(B), because (A) is conceptually simpler than (B).
Do you already know which of these two ways will be used in the DocBook file
that will be the output of w2x (if chosen for DocBook)?
I'm sorry but we cannot give a clear answer here.
I've re-read the relevant sections in
- Office Open XML File Formats — Fundamentals and Markup Language Reference
- DocBook 5.1: The Definitive Guide
before writing this email and which of (A) and (B) we'll choose to
implement the feature you want (indexed terms which point to ranges) is
currently far from being crystal-clear.
--
XMLmind Word To XML Support List
[email protected]
http://www.xmlmind.com/mailman/listinfo/w2x-support
