Re^9: Converting Unicode

Expecting the programming language to magically default HTML or relational databases to UTF-8 is quite a stretch.

Like expecting that human programmers automatically default to octal system to avoid future rounding errors with floats.

It's just outside the realm of the programming language.

Cheers Rolf
_{(addicted to the Perl Programming Language :)

see Wikisyntax for the Monastery}

Comment on Re^9: Converting Unicode

Replies are listed 'Best First'.
Re^10: Converting Unicode by Polyglot (Chaplain) on Dec 04, 2023 at 22:39 UTC
No, I don't think it's a stretch. It will happen in due time. Soon everyone will be working with UTF8 by default, or some near equivalent of it (utf8mb4?). I think it might already be the standard if it weren't resisted by those slow to adopt it. Blessings, ~Polyglot~	[reply]
Re^11: Converting Unicode by LanX (Saint) on Dec 05, 2023 at 00:21 UTC
> with UTF8 by default, or some near equivalent of it (utf8mb4?) And you are contradicting yourself by proposing two defaults at the same time. So 5 years from now on someone like you will complain the wrong one was chosen. Neither HTML nor table/db/schema encodings are part of the language and magically changing their settings/headers would not only require new modules and procedures. (Not sure if CGI.pm is even actively developed anymore.) It would also mean magically overriding the configs of the Web/DB servers. > I don't think it's a stretch Well, who else thinks like you? Which language does it like you propose? Cheers Rolf _{(addicted to the Perl Programming Language :) see Wikisyntax for the Monastery}	[reply]