08521: tascr30: Locale setting causes .lay parser error

ID	Category [?]	Severity [?]	Reproducibility	Date Submitted	Last Update
08521	Graphics	Minor	Always	Nov 28, 2022, 12:21	Nov 28, 2022, 15:51

Tester	hap	View Status	Public	Platform	MAME (Official Binary)
Assigned To	cuavas	Resolution	Fixed	OS	Windows 10/11 (64-bit)
Status [?]	Resolved			Driver	chess/tasc.cpp
Version	0.249	Fixed in Version	0.250	Build	64-bit
		Fixed in Git Commit	b36c7a9	Github Pull Request #

Summary	08521: tascr30: Locale setting causes .lay parser error
Description	Locale setting causes .lay parser error. There's a bug either in the XML parser or rendlay. It's not specific to tascr30, it also happens with renaissa, maybe more artwork is affected too.
Steps To Reproduce	- change OS decimal point setting to comma (commonly, it's a dot. On non-English Windows it may be a comma already) - mame tascr30 - notice the leds are placed wrong - don't forget to change OS setting back
Additional Information	Reported to me by Luis on a German forum. I was told 0.236 is the last version where the bug does not happen.
Github Commit

Flags
Regression Version	0.237
Affected Sets / Systems	tascr30

Attached Files	tascr30_good.png (89,518 bytes) Nov 28, 2022, 12:24 Uploaded by hap
	tascr30_wrong.png (89,476 bytes) Nov 28, 2022, 12:24 Uploaded by hap
	Screenshot (346).png (80,544 bytes) Nov 28, 2022, 12:34 Uploaded by hap

No.20867 hap Developer Nov 28, 2022, 12:28	If it helps, maybe Tafoid can run the screenshot comparison tool, see how many internal .lay files are affected.
No.20868 cuavas Administrator Nov 28, 2022, 15:03	If it started on Windows with ac9ca1d020ae9d1f335f7bbb8876680d5fb41603, it was probably happening on macOS for a lot longer.
No.20869 cuavas Administrator Nov 28, 2022, 15:51	Not strictly a “parsing” error – the error actually crept in when a layout parameter containing a floating-point number is used as a string.