Re: Racy NLS behaviour in FAT (and possible other fs)

OGAWA Hirofumi wrote: > Yes. But sorry, I don't have any plan and time to fix it now. > I know the feeling. :) I just wanted to know where things stand as I have little insight into vfat development. > If you are using "iocharset=utf8" now, "codepage=cp???,iocharset=xxx,utf8" > might help a

Re: Racy NLS behaviour in FAT (and possible other fs)

Pierre Ossman <[EMAIL PROTECTED]> writes: > OGAWA Hirofumi wrote: >>> I'm experiencing a rather odd behaviour with the character set >>> conversion. If I mount a vfat fs with utf8 and then create a file >>> with invalid utf-8 sequences, the file will briefly exist with these >>> invalid

Re: Racy NLS behaviour in FAT (and possible other fs)

OGAWA Hirofumi wrote: >> I'm experiencing a rather odd behaviour with the character set >> conversion. If I mount a vfat fs with utf8 and then create a file >> with invalid utf-8 sequences, the file will briefly exist with these >> invalid sequences, then quickly convert to a stripped version. >>

Re: Racy NLS behaviour in FAT (and possible other fs)

Pierre Ossman <[EMAIL PROTECTED]> writes: > Hi, Hi, > I'm experiencing a rather odd behaviour with the character set > conversion. If I mount a vfat fs with utf8 and then create a file > with invalid utf-8 sequences, the file will briefly exist with these > invalid sequences, then quickly

Racy NLS behaviour in FAT (and possible other fs)

Hi, I'm experiencing a rather odd behaviour with the character set conversion. If I mount a vfat fs with utf8 and then create a file with invalid utf-8 sequences, the file will briefly exist with these invalid sequences, then quickly convert to a stripped version. I haven't found an easy way to

Racy NLS behaviour in FAT (and possible other fs)

Hi, I'm experiencing a rather odd behaviour with the character set conversion. If I mount a vfat fs with utf8 and then create a file with invalid utf-8 sequences, the file will briefly exist with these invalid sequences, then quickly convert to a stripped version. I haven't found an easy way to

Re: Racy NLS behaviour in FAT (and possible other fs)

Pierre Ossman [EMAIL PROTECTED] writes: Hi, Hi, I'm experiencing a rather odd behaviour with the character set conversion. If I mount a vfat fs with utf8 and then create a file with invalid utf-8 sequences, the file will briefly exist with these invalid sequences, then quickly convert to a

Re: Racy NLS behaviour in FAT (and possible other fs)

OGAWA Hirofumi wrote: I'm experiencing a rather odd behaviour with the character set conversion. If I mount a vfat fs with utf8 and then create a file with invalid utf-8 sequences, the file will briefly exist with these invalid sequences, then quickly convert to a stripped version.

Re: Racy NLS behaviour in FAT (and possible other fs)

Pierre Ossman [EMAIL PROTECTED] writes: OGAWA Hirofumi wrote: I'm experiencing a rather odd behaviour with the character set conversion. If I mount a vfat fs with utf8 and then create a file with invalid utf-8 sequences, the file will briefly exist with these invalid sequences, then quickly

Re: Racy NLS behaviour in FAT (and possible other fs)

OGAWA Hirofumi wrote: Yes. But sorry, I don't have any plan and time to fix it now. I know the feeling. :) I just wanted to know where things stand as I have little insight into vfat development. If you are using iocharset=utf8 now, codepage=cp???,iocharset=xxx,utf8 might help a bit.