You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
An analyst created a Debrief plot, containing track and narrative data. He saved and closed the plot.
When he re-opened the plot, he got XML warnings, like: Character reference "" is an invalid XML character.
The document had around 200 instances of this character sequence.
Using a text editor he replaced those instances with a space, and the file loaded correctly.
It's a surprise that a new issue arose with XML import, since it's relatively mature code. The change in data may have been associated with the introduction of Pepys into the tool-chain.
Debrief should not save invalid XML characters to file when it saves to DPF.
I don't think we can overcome the issue on import, since the warning is probably thrown in the low-level XML parsing, before control gets to our handlers.
The text was updated successfully, but these errors were encountered:
An analyst created a Debrief plot, containing track and narrative data. He saved and closed the plot.
When he re-opened the plot, he got XML warnings, like:
Character reference "" is an invalid XML character.
The document had around 200 instances of this character sequence.
Using a text editor he replaced those instances with a space, and the file loaded correctly.
It's a surprise that a new issue arose with XML import, since it's relatively mature code. The change in data may have been associated with the introduction of Pepys into the tool-chain.
Debrief should not save invalid XML characters to file when it saves to DPF.
I don't think we can overcome the issue on import, since the warning is probably thrown in the low-level XML parsing, before control gets to our handlers.
The text was updated successfully, but these errors were encountered: