Antony Blakey wrote: > >> For book/title, select the title and replace it by info(title). See >> attached screenshot. > > Which would be fine, except as you can see from the screen grab, I have > 2 info(no_title) replacement options, and no info(title) options.
That's right. This is a *random* bug (because sometimes you'll see info(no_title), info(title); e.g. in the screenshot I've sent you) we fixed yesterday. What follows is an excerpt of our next changes.html file: --- When replacing the title element of a DocBook 5 book, the Edit tool randomly suggested the following pairs of element templates: info(no_title), info(title) and info(no_title), info(no_title). The Edit tool now always suggests info(no_title), info(title). If you need to add meta-info to a DocBook 5 book, please restrict yourself to replacing its title element by an info(title) template. Do not replace the title element by info(no_title) and do not insert info(no_title) after the title element as this would cause XMLmind XML Editor to automatically switch to lenient mode. This limitation is specific to the title and meta-info of a book (because the title element is optional in info(title) which makes the content model *truly* *ambiguous*). There is no such problem for the title and meta-info of a chapter or a section. --- > >> The other option, Insert info(no_title) after the title is still >> considered to be ambiguous by XMLmind XML Editor, so don't use it. > > It would be good if this were indicated in the interface in some way. The document templates for DocBook 4 and DocBook now come with bookinfo, articleinfo, info(title), etc, in standard instead of a bare title because [1] this seems to be what the user generally wants [2] this should avoid the problem you faced in the vast majority of cases. > BTW, I've used oxygen in the past, although your styled editing is > better which is what I'm evaluating now. However one of the first things > I noticed about the XXE vs. oxygen is that oxygen uses native open/save > dialogs. It makes a big difference to the impression of the product - on > the Mac, particularly. Thank you for this feedback and also thank you very much for taking the time to report this problem.
