On 13/02/2021 14:01, Mayayana wrote:
> "Ahem A Rivet's Shot"  wrote
>
> | > The 'modern' way to handle extended/extra characters is UTF
> |
> | It is, perhaps, worth adding that the reason that this is the
> | modern way is that it is the *only* encoding capable of representing
> | everything unambiguously.
> |
>
>    More to the point, it's backward compatible with HTML,
> where the vast majority of webpages are still effectively
> ASCII, aside from the odd curly quote or space character
> inserted by editor software. Anything else would have
> required multi-byte characters for the ASCII range and
> thus would have broken editors and webpages.
>
>    This way we can espouse the value of multiculturalism
> without changing very much. :)
>
>
Does any one else suspect that this post is utter bunk? UTF 8 is
multibyte character sequences and its not necessarily compatible with
HTML which uses straight, not curly, brackets.

UTF8 is a layer above HTML. Its down to the browser and it's access to
fonts to render it correctly and the server to specify that its in use.


--
"In our post-modern world, climate science is not powerful because it is
true: it is true because it is powerful."

Lucas Bergkamp

--- SoupGate-Win32 v1.05