Magnus G?fvert wrote: > > I am editing a user manual in DocBook v5+ format using XXE Professional > Edition 4.5.0 and have severe problems with creating an index: > > First, the DocBook > Insert or edit index term menu item is always > disabled. It seems it only works with DocBook, i.e. v4. >
I'm sorry but I cannot reproduce this behavior with any of our DocBook 5 documents. See attached screenshot of XXE_install_dir/demo/docbook5-sample.xml. "DocBook > Insert or edit index term" is disabled in very few cases, only when: * The DocBook 5 grammar does not allow to insert an indexterm at caret position (e.g. inside a pubdate). * The element containing the caret is read-only (e.g. inside an inclusion). May be it does not work because your DocBook 5 document is invalid? May be XXE silently crashes when you use "DocBook > Insert or edit index term"? See http://www.xmlmind.com/xmleditor/faq.html#display_exception_in_console > I could live with this it was possible to manually insert indexterm > elements. "DocBook > Insert or edit index term" is by far the safest and quickest way to insert indexterms. That's why we really need to solve this problem. Please try to explain us step by step how to reproduce this problem. > However, it is not possible to select a word in para#text and > Convert [wrap] an indexterm. It is simply not shown as an alternative. "Convert [wrap]", a generic, low-level, command, simply cannot convert some text to an indexterm. > I can insert an indexterm(singular), but it is not possible to position > the caret inside it and I cannot figure out how to add content. If I > select the (empty) indexterm the DocBook > Insert or edit index term is > enabled, but when I select it I am presented with an error dialog > claiming that "The selected index term is invalid or inconsistent: Some > required information is missing. [term1]". Yes, that's right. We managed to reproduce this behavior. This is a kind of bug. "Insert indexterm(singular)" inserts a completely empty indexterm element. You are expected to first manually insert a <primary> child inside the <indexterm> before being able to type a term. (A completely empty indexterm element is valid because of the way the DocBook 5 grammar has been written.) However, this is highly non intuitive. That's why we have improved the indexterm(singular), indexterm(startofrange), indexterm(endofrange) element templates in both the DocBook 4 and DocBook 5 configurations. You'll find this bug fix in XXE v4.5.1 which should be released today. -------------- next part -------------- A non-text attachment was scrubbed... Name: insert_index_term_in_db5.png Type: image/png Size: 95172 bytes Desc: not available Url : http://www.xmlmind.com/pipermail/xmleditor-support/attachments/20091126/6e1a1c8c/attachment-0001.png
