On 09/14/2011 05:27 PM, Yves Forkl wrote: > > we have encountered a rather strange behaviour of XXE in the Tree view > display. > > We normally work in the Styled view defined by a configuration of our own, > which is derived from XXE's DocBook configuration. But sometimes we need to > switch to the Tree view, especially when editing "tiny little" XML structures. > > My observation is that in Tree view, the text nodes within specific element > types are displayed in a different, Courier-like font. Some (but not all) of > the elements affected are specific to our configuration, i.e. they are not > part of the DocBook elements and hence are unknown in XXE's stock > configuration for DocBook. (This might explain why I could not reproduce the > behaviour with a DocBook document.) > > Why is the font change relevant?
The tree view automatically displays text nodes contained in elements having xml:space="preserve"[*] using a monospace font and a light gray background. > Because with XXE 4.8.0 under Windows (not so under Linux), certain characters > actually "disappear" when displayed in the Courier-like font! This means, it > is impossible to select them or to put the cursor at them, in Tree view only. > So far this has occurred for one character: U+2009 THIN SPACE. > Some fonts are missing glyphs for certain characters. Normally in such case, Java renders the character as a small rectangle. A few exotic characters cause the text line to be rendered with an incorrect horizontal distance between the characters. Unfortunately, there is nothing we, XMLmind, can do to fix these two problems. > This is rather troubling because if narrow spacing characters like U+2009 are > already hard to see (and to select) in Styled view, it is really confusing > when you wonder if they are completely gone, after having switched to Tree > view. > > Now, to solve the problem, I think it should be sufficient to prevent the > font change that occurs (in my case) for non-DocBook elements, because I > suspect that U+2009 is simply dropped somehow in that monospace font. Any > hints on how to do this? See above. Also note that, as of v4.7, the tree view is completely configurable in terms of colors and fonts. This means that you can choose an alternate monospace font. See: * http://www.xmlmind.com/xmleditor/_distrib/doc/help/viewOptions.html#treeViewSettings * http://www.xmlmind.com/xmleditor/_distrib/doc/help/com.xmlmind.xmleditapp.kit.prefsheet.TreeViewSettingsEditor.html > > I am willing to set up a test case, but would prefer to know before on what > aspects I should focus. > I don't think you have found a problem in XXE that we, XMLmind, can solve. However, if you think that the problem actually comes from XXE, then we really need a test case. --- [*] Also, elements declared in the preserveSpace configuration element are treated as if they had xml:space="preserve". See http://www.xmlmind.com/xmleditor/_distrib/doc/configure/preserveSpace.html -- XMLmind XML Editor Support List [email protected] http://www.xmlmind.com/mailman/listinfo/xmleditor-support
