WHY YOU SHOULD NOT PARSE LOCALIZED STRINGS

Summary from the TLDR Web Dev newsletter

Parsing localized strings is problematic because the interpretation of numbers and dates varies a lot across locales, leading to ambiguity and errors. User device language may not reflect their intended input, and multiple valid string formats can represent the same data. Locale data also changes over time, leading to inconsistent results. Instead of parsing, use dedicated input mechanisms or standard interchange formats to handle user input and data exchange, respectively.