Andy Black wrote:
>
> In our XXE configuration files, we have an element (called 'example')
> with an attribute (called 'num') that is an ID according to the DTD. We
> show this attribute via the CSS configuration like this:
>
> example:before
> {
> content: "("
> text-field(attribute, num, columns, 10, font-size, small)
> ") "
> ;
> background-color:example-background-color();
> }
>
> If a user types an invalid ID in this text field (say by inserting a
> space in the middle: "xGoyo Jotama"), then XXE nicely beeps and does not
> let the user go on. If, however, the user does not understand what XXE
> is trying to say and chooses to click on the File Save tool bar button,
> the invalid ID is saved in the file and the user can merrily go on to
> other editing. (XXE does indeed immediately record the fact that this
> is wrong by showing the error icon in the status bar. Unfortunately,
> some of our users do not necessarily pay attention to this icon.)
May be you should turn on the "Automatically show Validity tool" option
See
http://www.xmlmind.com/xmleditor/_distrib/doc/help/com.xmlmind.guiutil.PreferencesEditorDialog.html#validateOptions
>
> I notice that the same behavior is not possible when using the Attribute
> Edit tool. If one types in a space in the middle of this ID attribute
> and does a File Save operation, the attribute is not saved with space.
> This is the kind of behavior I was expecting since it then maintains the
> integrity of the XML file.
>
> So my question is, is this behavior in the text-field (where it is
> possible to produce ill-formed XML) intentional
Not ill-formed. Invalid.
> or is this possibly a
> bug? This happens with Personal Edition XXE 4.5.0 and XXE 4.5.1 (and
> possibly earlier versions, too, but I only tried these two).
>
We knew about this behavior. I'm sorry to inform you that we currently
don't see how to improve the situation.
