Comment 5 for bug 49217

Looking at dosfsck/file.c (around line 57), it appears that each character in the filename is expected to be independent. According to http://download.microsoft.com/download/1/6/1/161ba512-40e2-4cc9-843a-923143f3456c/fatgen103.doc, it appears that any of the eight or three characters in the 8.3 format may be DBCS character pairs, rather than single-byte characters (and as such, not unsigned char).

Ideally, dosfsck should take a codepage argument to assign the OEM codepage for the FAT32 filesystem, and expect either single-byte or DBCS encoding depending on the provided codepage.

Further, any automated execution of dosfsck (e.g. prior to resizing a partition in the installer) should use the default OEM codepage for the installation locale.