Messages in this thread | | | From | OGAWA Hirofumi <> | Subject | Re: vfat: Broken case-insensitive support for UTF-8 | Date | Tue, 21 Jan 2020 21:26:34 +0900 |
| |
Pali Rohár <pali.rohar@gmail.com> writes:
> On Tuesday 21 January 2020 12:52:50 OGAWA Hirofumi wrote: >> BTW, VFAT has to store the both of shortname (codepage) and longname >> (UTF16), and using both names to open a file. So Windows should be using >> current locale codepage to make shortname even latest Windows for VFAT. > > fastfat.sys stores into shortnames only 7bit characters. Which is same > in all OEM codepages. Non-7bit are replaced by underline or shortened by > "~N" syntax. According to source code of fastfat.sys it has some > registry option to allow usage also of full 8bit OEM codepage. > > So default behavior seems to be safe.
Are you sure if default is 7bit only? I'm pretty sure, at least, old Windows version stored 8bit chars by default install.
Thanks. -- OGAWA Hirofumi <hirofumi@mail.parknet.co.jp>
| |