Understanding Surrogate Pairs: Why Some Windows Filenames Can't Be Read

Post by rstuart4133 » Wed, Feb 26, 2025, 9:42 PM UTC

dwdz wrote: post #50

feldrim wrote: post #22

Earlier quoted context omitted.

Oh, great. Can you also share the locale? I'll write another Postscriptum section then.

LANG=en_IE.UTF-8 LANGUAGE=en_IE:en LC_CTYPE="en_IE.UTF-8" LC_NUMERIC="en_IE.UTF-8" LC_TIME="en_IE.UTF-8" LC_COLLATE="en_IE.UTF-8" LC_MONETARY="en_IE.UTF-8" LC_MESSAGES="en_IE.UTF-8" LC_PAPER="en_IE.UTF-8" LC_NAME="en_IE.UTF-8" LC_ADDRESS="en_IE.UTF-8" LC_TELEPHONE="en_IE.UTF-8" LC_MEASUREMENT="en_IE.UTF-8" LC_IDENTIFICATION="en_IE.UTF-8" LC_ALL=

Post by afiori » Thu, Feb 27, 2025, 7:24 AM UTC

formerly_proven wrote: post #30

zombot wrote: post #28

Earlier quoted context omitted.

Microsoft never implements a standard, they only ever implement their own shit. Sometimes it's a close enough parody of a standard to fool superficial onlookers, but that's as close as you'll ever get.

Java, NT, .NET, "wide" C and C++ and a few others from the same time frame ended up with WTF-16 because surrogate pairs didn't exist when they were designed. They were designed with UCS-2, which is a fixed-length encoding. Unicode 2.0 then extended that to be variable length (16/32-bit) using surrogate pairs and that's where all the systems come from which don't validate surrogate pairs.

Post by account42 » Thu, Feb 27, 2025, 11:07 AM UTC

FirmwareBurner wrote: post #34

zombot wrote: post #28

Earlier quoted context omitted.

Microsoft never implements a standard, they only ever implement their own shit. Sometimes it's a close enough parody of a standard to fool superficial onlookers, but that's as close as you'll ever get.

>Microsoft never implements a standard Win32 ?