James J. Ramsey wrote: > If the option "Save characters outside encoding as > entity references" is checked, then when I use the > insertCharByName dialog to insert the entity "“" > into a DocBook file, the entity "&rdquor" gets written > to the file instead instead.
There is a misunderstanding. Internally, XXE has no concept of ``entity'' at all. See http://www.xmlmind.com/xmleditor/detailed_features.html#nonfeatures Command insertCharByName does not insert an *entity reference* in a DocBook *file*. It inserts a *character* in the *logical content* (AKA infoset) of a DocBook document. Command insertCharByName must be seen as an alternative user interface to the Character tool. However, in order * to improve the readability of XML files using a text editor, * AND to ease switching to an XML editor other than XXE, by default, when the document is saved to a file, characters outside the target encoding of the save file, such as "U+201C" for say ISO-8859-1, are saved as "&XXX;" (of course, only when char entity "XXX" has been *properly* declared in the DTD). > Also, using the > insertCharByName dialog to insert the entity "‘" > into a DocBook file causes the entity "&rsquor" to > written to the file instead instead. This problem > seems to result because in DocBook 4.2, “ and > ” refer to the same Unicode character U+201C, > while ‘ and ’ refer to the same Unicode > character U+2018. > > To further complicate matters, it looks like “ > and ” were never meant to be equivalent; it's a > DocBook bug. In DocBook 4.3, it will ” and > ” that will be equivalent, with ” > referring to character U+201D. It's a similar story > with ‘ and ’, with &rsquor referring to > U+2019. DocBook 4.3 will be included in XXE as soon as it will be officially released. Meanwhile, you can fix your problem * by updating your DocBook entity files, * OR switch to an XML editor designed to edit the *physical content* of an XML document.
