On 09/23/2019 09:21 AM, Louise Prompers wrote:
Thank you for the research and work concerning this issue. To achieve our
goals, we can make multiple bookmarks in Word for the same range, if we want to
reference to it multiple times. I have tested this and this works well.
The see-reference instead of the single primary reference, for the second
indexterm referring to the same range, is actually not really an improvement
for us. If Subject B gets a see-reference to Subject A, that means the user
will have to look up all the page numbers pertaining to Subject A, and it is
possible that we mean only to reference Subject B to the range (that is the
same for Subject A and B). Would it be better to change this feature again to
the way it was in w2x v1.7?
Sorry but the answer is no. The change in XMLmind Word To XML v1.8 is
documented as being a *bug* *fix*, not as being an enhancement. It makes
for us no sense to remove a bug fix.
Excerpts from v1.8 Change history
---
Bug fixes:
...
* First index entry marking a given page range (e.g. field
XE "XML" \r "OpenXMLPageRange") in the DOCX document was correctly
converted to an DITA or DocBook index term range (e.g. <indexterm
start="OpenXMLPageRange">XML</indexterm> and <indexterm
end="OpenXMLPageRange"/>), but subsequent index entries marking the same
page range (e.g. field XE "Extensible Markup
Language" \r "OpenXMLPageRange") were converted to single point index
terms (e.g. <indexterm>Extensible Markup Language</indexterm>).
Now subsequent index entries marking the same page range are converted
to index terms containing a redirection to the first index term
referencing of this page range (e.g. <indexterm>Extensible Markup
Language<index-see>XML</index-see></indexterm>).
---
--> Your workaround for this v1.7 bug is:
---
To achieve our goals, we can make multiple bookmarks in Word for the
same range, if we want to reference to it multiple times. I have tested
this and this works well.
---
That is, you use bookmarks to create multiple ranges all having
*different* *names*, but all these ranges happen to have exactly the
same boundaries.
Therefore I don't see how our v1.8 bug fix could break anything in what
you did.
--
XMLmind Word To XML Support List
[email protected]
https://www.xmlmind.com/mailman/listinfo/w2x-support