We've had similar issues with clients using 1-2-1 as a meeting type name. When data about those records are exported to CSV and loaded by Excel, it gets seen as the date 2001-02-01 (or, presumably, 2001-01-02 for those using a US locale in their setup)
even if the value is quoted (which we hoped would be interpreted as "this value is definitely nothing fancier than a basic string", but it was not).
> This standard is from 2005 and it is pretty clear that it is not universally used.
Unfortunately a lot of non-conforming software can't change or they risk compatibility problems with old versions of themselves. 2005 is relatively recent in the history of CSV files.