Messages in this thread | | | From | "Petr Vandrovec" <> | Date | Mon, 3 Jul 2000 22:32:28 MET-1 | Subject | Re: [patch] forward port of 16 bit nls (vfat, ntfs, ncpfs, |
| |
On 3 Jul 00 at 22:23, Urban Widmark wrote: > > If you could build utf8 conversion table for me to use it in place of > > iocharset and/or codepage, I'll be very happy to test multibyte encodings, > > but it is a bit complicated to verify them without real world examples... > > I don't understand, utf8 conversion table? fs/nls/nls_base.c has > conversion routines for utf8. Or do you mean tables showing what output to > expect, a file named xyz would show up as X in utf8?
Yes. So that I could remove tests of 'utf8' in fs/ncpfs/ioctl.c... Pardon my ignorance, but I know no method to deliver utf8 encoded filename to userspace, except doing encoding with utf8_mbtowc/_wctomb... :-( If this could be handled with nls_table, I could remove some ifs from my code (currently ncpfs accepts 'utf8' string for iocharset and handles it on its own, as some people required passing utf8 paths to userspace...)
> You could try the "abc" charset for testing that the fs code is ok with > chars wider than > 1 byte. Multibyte chars in readable ascii, should > behave just like the 16bit codepages.
I'll try that. Thanks, Petr Vandrovec vandrove@vc.cvut.cz
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.rutgers.edu Please read the FAQ at http://www.tux.org/lkml/
| |