View Issue Details

IDProjectCategoryView StatusLast Update
0000738OpenIVTools - Text Editorpublic2020-07-22 22:01
ReporterBobRossAssigned ToTeam 
Status resolvedResolutionfixed 
PlatformWindowsOS10 (64-bit, 32-bit)OS Version10.0
Product Version4.0.1 
Target Version4.1Fixed in Version4.1 
Summary0000738: Invalid XML exported by "Export to XML" feature
DescriptionCurrently when exporting XML, the first tag in the file will start with a "0". This is considered invalid XML, as XML tags cannot start with numbers, punctuation, or the letters "xml". Please consider fixing this at some point.

Full XML guidelines state that XML elements must follow these naming rules:
- Names can contain letters, numbers, and other characters
- Names cannot start with a number or punctuation character (this is this issue)
- Names cannot start with the letters xml (or XML, or Xml, etc)
- Names cannot contain spaces

Thank you.
Steps To Reproduce1. Find any YMT file or similar allow you to export the file to XML.
2. Utilize the export feature or just open the text editor which produces the same affect.
3. Inspect the exported XML file or text editor, the first key is not prefixed with "UNK_MEMBER_" (which would be valid) but instead is similar to "0xB2512452".
Additional InformationFile used for reproduction: "update.rpf\x64\data\itemdatabase\catalog_awards_mp.rpf\catalog_awards_mp.ymt"

Low priority, would be a "nice to see fixed".
GameRed Dead Redemption 2


There are no notes attached to this issue.

Issue History

Date Modified Username Field Change
2020-06-25 11:32 BobRoss New Issue
2020-06-25 11:35 BobRoss Tag Attached: XML
2020-06-26 11:03 Team Assigned To => Team
2020-06-26 11:03 Team Reproducibility always => sometimes
2020-06-26 11:03 Team Status new => assigned
2020-06-26 11:03 Team Target Version => 4.1
2020-06-26 11:03 Team Summary Invalid XML exported by recent "Export to XML" feature => Invalid XML exported by "Export to XML" feature
2020-07-22 22:01 Team Status assigned => resolved
2020-07-22 22:01 Team Resolution open => fixed
2020-07-22 22:01 Team Fixed in Version => 4.1