The SDK contradicts itself regarding XML encoding:
IMPORTANT! When creating or editing any XML file, you must ensure that it
is saved using a UTF-8 BOM encoding! Any other encoding may cause issues,
especially if the add-on is destined for publishing on the Xbox.
then later:
Editing Files
When creating or editing any XML file, you must ensure that it is saved
using a UTF-8 encoding (without BOM). Any other encoding may cause issues
when published. Also keep in mind that XML files with an `` header should also
specify “utf-8” for the encoding attribute, for example:
This does not encode the file itself, but does provide a hint to the text
parser that the file is using this encoding. To encode the file correctly, you
can use the options within the text editor that you use. For example, in
Notepad++:
So which is it? UTF-8 or UTF-8-BOM?