Validate XML Config with UTF-8-BOM Encoding

[PatrickGrub]

We have experienced a lot of problems when Importing an XML Config which is not UTF-8-BOM:

• This is very hard to identify
• The solution is to change the Encoding before Importing to "Utf-8-BOM"

In order to force everybody to use UTF-8-BOM:

• [ ] The menu command "Save powerGate config" should verify if the encoding is "Utf-8-BOM" and if not then bring a message "The Encoding of the XML must be 'UTF-8-BOM', please change the encoding and import it again!"

[TollJulian]

Unfortunately I found no way to load a XML file with Byte Order Mark from Vault Options, so the export from Vault Options will fail. I've tried loading with:

direct conversion: $xml = xml$xmlString In any way it throws the Error "Invalid Data at the Root level"

the only way to use a file with BOM encoding is to remove the Byte Order Mark before the import (for UTF-8-BOM remove the first 3 bytes), but this would convert the file back to UTF-8

I suggest to work with UTF-8 and avoid any special character in the config file