On Monday, 27 December 2021 at 14:30:55 UTC, Adam D Ruppe wrote:
Most unix things do utf-8 more often than not, but technically
you are supposed to check the locale and change the terminal
settings to do it right.
Cool! I mean, I don't plan on supporting legacy systems so I
think we're fine if the up-to-date systems fully support UTF-8 as
the default.
You should ALWAYS use the -W suffix functions on Windows when
available, and pass them utf-16 encoded strings.
There's a bunch of windows things taking utf-8 nowdays too, but
utf-16 is what they standardized on back in the 1990's so it
gives you a lot of compatibility. The Windows OS will convert
to other things for you it for you do this utf-16 consistently.
That's pretty nice. In this case is even better because at least
for now, I will not work on Windows by myself because making the
library work on Linux is a bit of a challenge itself. So I will
wait for any contributors to work with that and they will
probably know how windows convert UTF-8 to UTF-16 and they will
be able to do tests. Also I plan to support only Windows 10/11
64-bit officially so just like with Unix, I don't mind if legacy
systems don't work.
The Windows API is an absolute pleasure to work with next to
much of the trash you're forced to deal with on Linux.
Whaaaat??? Don't crash my dreams sempai!!! I mean, this may sound
stupid but which kind of API you are referring to? Do you mean
system library stuff (like "unistd.h" for linux and "windows.h"
for Windows) or low level system calls?
