Quote:
Originally Posted by Puni
Thanks that's lead to a few answers. Since automatic romanization of DBCS characters can easily turn a single Japanese kanji to 6-8 characters in (what looks like) Pinyin, it's going to overrun the NTFS limit really fast and middle-out truncation of that is making it a hot mess. I'm looking at the author's comments on UTF-8 settings in the OS but it's not clear how that corresponds to Windows 11 controls, which has separate language controls for IME, Locales, as well as Explorer localization only. UTF-8 is natively supported in the FS but I'm suspecting he is referring to locale which changes how shell applications handle data input.
|
I suspect you mean "the Windows limit".
BR