>> Often the software doesn't take into account how things work in other languages Not just languages. In my area we run into constant issues with MS products

>> Often the software doesn't take into account how things work in other languages Not just languages. In my area we run into constant issues with MS products using American date/time formats in places it isn't wanted. For half of ever month this is a big deal, even inside the US as many organizations use the international standard. People cut-and-paste from popup windows or error logs only to discover that the tiny bit of MS code that generated the notice doesn't respect realworld date formats (day-month-year) and just defaults to the US format (month-day-year). Non-MS software (apple/google) and open source more often than not respect date formats. It is MS that seems to just not care. I was once involved in a heated debate re a contract when everyone suddenly realized the issue: 05/06/18 had been confused with 06/05/18, resulting in an extra month of costs being attached. I think to avoid further ambiguity I jokingly rewrote it as "On the sixth day of the fifth month of the year of our lord two thousands and eighteen and ..."