June 16, 20178 yr Commercial Member Hello @ll, due to the many issues related to incorrect encoding of the primary config files, I have decided to change the way the Addon Organizer handles them. All "*.cfg" files are read and written in the encoding that they currently have. If that encoding is not as per specification, it will still be that way when you save it with AO. The XML files are forced to be XML spec compliant (UTF-8 with BOM) when you save them with the AO V4 only: The AO compiles a list of all files that it is reading in normal operations where the encoding is not as it should be. You can call up the list with a button on the main dialog. BE CAREFUL in V4: if you just leave the *.cfg files in an incorrect encoding, it is very likely that they will become unusable at some point. The safest strategy is to use the information in the AO encoding error list and switch them back to the encoding that they should have (Unicode = UCS-2 Little Endian). The exception are the XML files, which should have UTF-8 encoding. As long as the AO can read them, it will save them in the proper encoding automatically. So if you have a lot of encoding errors with XML files, first try to simply save them with AO, then take a look at the list again. http://lorby-si.weebly.com/downloads.html Best regards LORBY-SI
Archived
This topic is now archived and is closed to further replies.