On 13/02/2021 21:49, TimS wrote:
> On 13 Feb 2021 at 21:05:47 GMT, Ahem A Rivet's Shot 
> wrote:
>
>> On Sat, 13 Feb 2021 14:42:37 -0500
>> "Mayayana"  wrote:
>>
>>>     So all I was saying was that UTF-8 was far easier than
>>>   any other approach, using "wide characters", when it came
>>>   time to fully support all languages under one system. Even now
>>>   I'm not sure how much it's really used.
>>
>>  Anyone who has to support multiple languages tends to use unicode
>> internally for the sake of sanity (I was for a while internationalisation
>> specialist (among other hats) on the Yahoo! front page team). We had loads
>> of fun with external feeds claiming to be ISO8859-1 and sending Win-1252 -
>> they're almost but not quite the same.
>
> I convert everything to UTF-8. Windows tends to lie about which code-page
it's
> using, anyway.
>
So does MAC OSX
UTF8 makes it all come right

It's surprising how often I need it - type CO₂ or 25°C or
ΔT=λC × ln(ΔCO₂) and you are in trouble without UTF8...


--
“There are two ways to be fooled. One is to believe what isn’t true; the
other is to refuse to believe what is true.”

—Soren Kierkegaard

--- SoupGate-Win32 v1.05