Re:I'm “still afraid to use spaces in file names” years old
by grishka on Thursday November 11, 2021 @01:29PM
(#29191264)
> since Windows is the only major OS that made the unfortunate choice of having the base character type 16 bits wide
Apple OSes use something they call "unichar" inside NSStrings. I'm not 100% sure what it is, but it feels like it's the same 16-bit wide character.
Re:I'm “still afraid to use spaces in file names” years old
by ziml77 on Thursday November 11, 2021 @03:20PM
(#29192639)
It's possible! It seemed like a sensible choice back in the early 90s when the answer to making a system for global use was UCS-2. I know Java was another one that went with that decision.
Re:I'm “still afraid to use spaces in file names” years old
by mjevans on Thursday November 11, 2021 @01:13PM
(#29191071)
I would rather they added a U suffixed version and better still backported that all the way to Win 7. Now in 3-7 years people can write programs that use the A functions, but have to check the version of Windows and refuse to run if it isn't new enough.
Re:I'm “still afraid to use spaces in file names” years old
by colejohnson66 on Thursday November 11, 2021 @06:19PM
(#29194503)
There’s been some talk of repurposing the A variants to work on UTF-8
Re:I'm “still afraid to use spaces in file names” years old
by account42 on Friday November 12, 2021 @06:37AM
(#29198272)
> All you have to do is request it in the application manifest and the A functions will accept and return UTF-8.
They really should have gone with WTF-8 [0] since the W functions generally accept WTF-16 and not just the valid UTF-16 subset.
Fortunately the future of the Windows API does look better since Microsoft has now added proper UTF-8 support since Win 10 1904. All you have to do is request it in the application manifest and the A functions will accept and return UTF-8.