Reply to thread

Message: <blockquote data-quote="jimmifett" data-source="post: 5440757" data-attributes="member: 55006">The XML is a complete disaster. You'd need a schema (a framework of how the xml is supposed to look) just to get started. Not impossible to create one, but then the XML itself is very poorly formatted, like someone hired a .Net dev that didn't know squat about using xml in thier code. You see, first create a schema and then run it through XSD.exe to generate classes to match the schema place them logical package/.Net namespace. Instead it looks like someone wrote thier own half-assed xml serialization code. There may or may not be a schema somewhere, but i'm willing to wager a donut that it's not validated against at any point in time, and certainly not using proper serialized output. Now, provided the xml was well formatted, and you have a good schema matched with it... it can be run through some xsl or even xsl:fo (likely the latter if you want pdf output) to generate formatted character sheets. Personally, i'd do this in java and use an XPath 2.0 capable parser, but can be done in any language that has an xsl:fo parser and preferably, tho not required (but it sure makes life easier!), supports XPath 2.0. Instead, it looks like they are doing some lame backend processing and generating a rather large image file that you have to download via silverlight for printing. Who ever came up with that genius idea should be denied bacon for life.</blockquote>