Christopher Smith wrote: > Gregory K. Ruiz-Ade wrote: >> Unless I'm just doing something wrong, here. If I can avoid this >> work, I'd be much happier. > > NTFS and HFS+ should both be able to handle unicode filenames. I believe > NTFS is limited to Unicode 1.x characters, but that would cover anything > that can be translated to ASCII for sure. >
I am aware of problems generally called filesystem encoding problems, but I have not played much with this. One such problem is archiving filenames on a system of one encoding into a tarball (or zipball), and extracting same on a system with a different encoding. I suppose the archiver interface ought to be able to translate (if there is a non-destructive translation), but I just haven't got around to looking at the situation. Not that it's so hard, I just haven't gottintuit. For your immediate needs, have you tried making your CD on a system with utf-8 filesystem encoding? I guess maybe Windows uses utf-16; here again are some simple experiments that I haven't gotten around to. Certainly, it would seem that reducing all filenames to ASCII might have some appeal, but then again that may be a short-sighted solution. Someday, non-unicode encodings will go away, at which time ASCII "translations" (mutations?) of non-ASCII will, at least, seem quaint. Such data will also interfere with searching mechanisms. Regards. ..jim -- [email protected] http://www.kernel-panic.org/cgi-bin/mailman/listinfo/kplug-lpsg
