Viewing Issue Advanced Details
|ID||Category [?]||Severity [?]||Reproducibility||Date Submitted||Last Update|
|06360||Interface||Minor||Always||Sep 1, 2016, 22:56||Sep 6, 2016, 16:19|
|Tester||ozfalcon||View Status||Public||Platform||MAME (Self-compiled)|
|Assigned To||Resolution||No change required||OS||Linux (32-bit)|
|Version||0.177||Fixed in Version||Build||Normal|
|Summary||06360: Create Config: When creating config files with -cc command, ini files are created with utf-8 bom at the start|
I had recycled an old ini file created by Mame -cc command and it failed because utf-8 bom at the start.
I'm not sure if the ini files created by Mame are supposed to have utf-8 bom at the start or not.
The Unicode Standard permits the BOM in UTF-8, but does not require or recommend its use.
|Steps To Reproduce||
Run Mame -cc command and inspect ini files for utf-8 bom at the start.
Stumbled across this via 06359
|Affected Sets / Systems||Create Config|
|There are no relationsihp linked to this issue.|
Sep 6, 2016, 02:37
|My .ini files are pretty old and they have the BOM at the beginning, and I've never had issue with them. I'll mark this as Direction Needed, since this is going to require some dev feedback.|
Sep 6, 2016, 16:19
|Text files created by MAME have had BOM inserted at the beginning since 0.111u2, when Unicode support was first introduced. OPEN_FLAG_NO_BOM, which disables this behavior, has existed since 0.117u3 but doesn't seem to have been used anywhere.|