Post by @mcc@mastodon.social

mcc

@mcc@mastodon.social 33 min. ago

https://learn.microsoft.com/en-us/windows/win32/intl/character-sets-used-in-file-names

"Character Sets Used in File Names

NTFS stores file names in Unicode"

MICROSOFT

MICROSOFT, THAT IS INADEQUATELY SPECIFIC

Character Sets Used in File Names - Win32 apps

NTFS stores file names in Unicode. In contrast, the older FAT12, FAT16, and FAT32 file systems use the OEM character set. For more information, see Code Pages.

0 Boosts

0 Likes

Kevin Boyd (he/him) 🇨🇦

@kboyd@phpc.social 7 min. ago

@mcc well at least it isn't mysql utf....

mcc

@mcc@mastodon.social 26 min. ago

Me, holding out two pieces of paper reading "UTF-16" and "UCS-2": I need you to document which of these your filesystem uses.

Pam from The Office: It's Unicode. — Me, holding out two pieces of paper reading "UTF-16" and "UCS-2": I need you to document which of these your filesystem uses. Pam from The Office: It's Unicode.

dana :Blobhaj_Witch:

@blinkygal@sunny.garden 20 min. ago

@mcc it is going to be UCS-2 validation just makes you need error handling:)

Howard Chu @ Symas

@hyc@mastodon.social 16 min. ago

@blinkygal @mcc Wikipedia claims Windows uses UTF-16. https://en.wikipedia.org/wiki/UTF-16

UCS-2 is now obsolete and dropped from the Unicode standard. But Windows was definitely all UCS-2 back in the NT / W2K era.

UTF-16

format for transforming texts encoded with one or two 16-bit code units per character of the universal character set defined by the ISO/IEC 10646 standard and the Unicode Standard

mcc

@mcc@mastodon.social 10 min. ago

@hyc @blinkygal Sorry when I say "is it UCS-2 or UTF-16" what I mean is "Is it valid UTF-16 or potentially-valid UTF-16, and also is any kind of normalization scheme in effect ever"

Howard Chu @ Symas

@hyc@mastodon.social 22 min. ago

@mcc back when NTFS was created, UTF-16 didn't exist. And there were no defined character codes outside the 16 bit character space.

mcc

@mcc@mastodon.social 18 min. ago

@hyc So… is it *actually* Unicode?

Howard Chu @ Symas

@hyc@mastodon.social 12 min. ago

@mcc is that a trick question? IME M$ never implements anything exactly in accordance with a published standard. Not even when they wrote the spec themselves.

1 more reply

phooky

@phooky@hexa.club 28 min. ago

@mcc Microsoft usually uses UTF-16; don't see why they'd mean anything else

mcc

@mcc@mastodon.social 25 min. ago

@phooky Okay but when we say "UTF-16" do we mean "UTF-16" or do we mean "Arrays of uint16_t which may, in some cases, parse as UTF-16"

BK Wooramel

@wooramel@furries.club 31 min. ago

@mcc Microsoft have always been the masters of giving technical advice that is precise, accurate, and entirely useless.

mcc

@mcc@mastodon.social 22 min. ago

@wooramel well what i'm afraid of is that it may not be precise or accurate (if it turns out that NTFS can store filenames containing pseudo-UTF-16 with invalid surrogate pairs)

Jo Shields

@directhex@tech.lgbt 31 min. ago

@mcc Microsoft usually means utf16 when they say Unicode

mcc

@mcc@mastodon.social 23 min. ago

@directhex ok but when they say UTF-16

do they mean UTF-16

or do they mean something else