Quote:
Originally Posted by BetterRed
The issue in question is not a 'bug', it's a legacy feature in a 40 year old application that is the most widely used in its class… by a country mile.
|
Actually utf-8 was only generally adopted in the 2008-2012 timeline and by Microsoft much later than that. So this "bug" was introduced in the last 15 years or so, so that Microsoft could keep using local 8 bit encodings like cp-1251 or cp-1252 when the world moved to unicode. Excel right now can read these files properly by importing them after setting the encoding.
Windows 11 should have fixed all this nonsense.