About .CFG files:
- We don't use the scenery.cfg anymore for our sceneries, but our software properly recognize if the scenery.cfg is encoded in UTF16LE (default), or if some other installer or the user has changed it in Ansi.
- We don't touch the add-ons.cfg file directly, but ask P3D to make all the needed changes for us.
- We don't touch the Prepar3D.cfg file, at all
About Simobject .CFG files:
- The simulator itself can read .cfg files encoded in both formats so, unless we had to use a non-Ansi characters in it, it would be useless to switch to UTF16, because it would result in doubling the file size with no benefit whatsoever
- If this was a problem (it's not), and an airplane.cfg or a sim.cfg didn't work, NO 3rd party airplane would work without converting the files, which is not obviously the case, precisely because the sim can recognize both encodings.
About .XML file:
XML files don't "have" to be encoded in any specific format. The only thing to be sure of, is the XML header (if present) must not conflict with the actual encoding of the file.