Non-alphanumeric characters are encoded in result of DescribeSchemaAsXml() API

[ronnielouie]

Using a feature source that contains non-alphanumeric characters (for example '$') in the class name or properties, perform a call to DescribeSchemaAsXml?() API. The returned result will contain an encoding of the character (for example -x24- to represent the '$' character).

[ronnielouie]

Changed FdoXmlFlags? NameAdjust? to false so that it does not encode the non-alphanumeric characters when writing to XML.

Fixed by submission  http://trac.osgeo.org/mapguide/changeset/1753 Fixed by submission  http://trac.osgeo.org/mapguide/changeset/1754

[chrisclaydon]

Rolled back by submission  http://trac.osgeo.org/mapguide/changeset/1797

Rolled back by submission  http://trac.osgeo.org/mapguide/changeset/1798

The problems caused by the escaping of characters that are not valid in XML element names that occurred in the schema report pages will be addressed in a different way.

[chrisclaydon]

The following two submissions fix the schema report pages to function correctly with the character escaping re-introduced by rolling back the previous changes:

Fixed by submission  http://trac.osgeo.org/mapguide/changeset/1807

Fixed by submission  http://trac.osgeo.org/mapguide/changeset/1808