Dwarf Fortress Bug Tracker - Dwarf Fortress
View Issue Details
0000404Dwarf FortressLegends Mode -- History Exportpublic2010-04-04 08:452010-12-09 17:38
Toady One 
lowmajorhave not tried
0000404: Legends XML export produces malformed XML
The XML file exported from Legends mode is illegal/not well-formed.
XML files must have a single top-level element that is parent of everything else. The file produced by DF has multiple elements at the top level, for example "regions", "underground_regions" and "sites" are all elements at top level.

The solution will be to wrap everything (except the <?xml?> prologue) inside a single top-level element, such as <world></world>.

I believe most XML parsers will bail on the file as it is now. (At least MSXML does: Try opening the file in Internet Explorer and scroll to the bottom, where you should see an error message.)
See XML 1.0 recommendation section 2.1: http://www.w3.org/TR/xml/#sec-well-formed [^]
legends, RESOLVED
Issue History
2010-04-04 08:45jfsNew Issue
2010-04-04 17:25QloosTag Attached: legends
2010-04-04 18:32SirPenguinNote Added: 0000971
2010-04-05 04:11SkibilianoIssue Monitored: Skibiliano
2010-05-01 16:21jfsNote Added: 0005861
2010-05-01 17:37smjjamesNote Added: 0005868
2010-08-30 02:22PhydauxIssue Monitored: Phydaux
2010-09-27 05:09Knight OtuNote Added: 0013020
2010-10-08 10:13jfsNote Added: 0013264
2010-10-08 10:13jfsTag Attached: RESOLVED
2010-12-09 17:38FootkerchiefStatusnew => resolved
2010-12-09 17:38FootkerchiefFixed in Version => 0.31.13
2010-12-09 17:38FootkerchiefResolutionopen => fixed
2010-12-09 17:38FootkerchiefAssigned To => Toady One

2010-04-04 18:32   
Just wanted to confirm this, though of course he did say that the feature was unfinished.
2010-05-01 16:21   
Just checked, this is still an issue in 0.31.03. Tested with a freshly generated pocket region.
2010-05-01 17:37   
Yea, Toady said that the export to xml isn't actually working yet.
Knight Otu   
2010-09-27 05:09   
As of 31.13, the exported xml has a wrapping <df_world> </df_world> element.
2010-10-08 10:13   
I can confirm that this bug is fixed.