When performing batch conversion of assets using the RC (see parent article) you can choose to perform XML conversion to binary format.
Binary XML conversion takes an input XML file, parses it, and stores the node tree in a binary format.
- Smaller file size
- Faster to read at runtime
- Filtered to contain only specific data
- Not human-readable
- Not human-editable
- Lossy conversion
In your Job XML file (see parent article), add a <Job> XML block in the <ConvertJob> group like follows:
In this example, the file 'xmlfilter.txt' is referenced, this file is located in Bin64\RC\xmlfilter.txt
This file controls which files are converted, and how.
The 'overwriteextension' property is used to force the files matching the input-set to be evaluated as if they were XML files (see parent document, on 'overwriteextension')
The file specified through the 'xmlfilter' property is formatted as text line, with each filter instruction on a separate line in the file.
While parsing this file, empty lines are ignored, all other lines must be formatted like one of the following:
A line starting with 'a' declares a filter on a XML attribute. Use the '*' wildcard to match multiple attribute names.
A line starting with 'e' declares a filter on a XML element. Use the '*' wildcard to mtach multiple element names.
The modifier for 'a' or 'e' can be either '+' (to include the matching XML data in the binary data) or '-' (to exclude the matching XML data)
A line starting with 'f table' declares a filter on XML files that will be subject to table-conversion from Microsoft Excel exported xml table format. Specify a file-mask to apply the filter to the files matching the mask. Use the '*' wildcard to match multiple files.
The filter file's element and attribute filters are evaluated top-down. The first matching rule for each XML item is selected to determine if it will be filtered out or not
If not element of attribute filter matches an XML item, it will not be filtered out.