Messages in this thread | | | Date | Mon, 13 Jun 2005 22:31:06 +0200 | From | Rutger Nijlunsing <> | Subject | Re: A Great Idea (tm) about reimplementing NLS. |
| |
On Mon, Jun 13, 2005 at 08:20:53PM +0100, Alan Cox wrote: > On Llu, 2005-06-13 at 18:20, Alexey Zaytsev wrote: > > Yes, that's how it works, but if I want ext or reiser or whatever to > > have NLS, I'll have to make them support it (btw, if I do so, wont it > > be rejected?). I want to move the NLS one level upper so the > > filesystem imlementations won't have to worry about it any more. I > > don't have much kernel experience, and none in the fs area, so I can't > > explain it any better, but hope you get the idea. > > An ext3fs is always utf-8. People might have chosen to put other > encodings on it but thats "not our fault" ;) > > There are some good technical reasons too > > Encodings don't map 1:1 - two names may cease to be unique > > Encodings vary in length - image a file name that is longer than the > allowed maximum on your system with your encoding choice - that could > occur with KOI8-R to UTF-8 I believe > > That said it ought to be possible to use the stackable fs work (FUSE > etc) to write a layer you can mount over any fs that does NLS > translation.
Or just make a symbolic linked shadow FS with translated filenames (UNTESTED):
cd /tmp cp -src /mnt/problem_dir . find problem_dir -exec bash -c "mv \'{}\' \'$(echo {} | iconv -f KOI8-R -t UTF-8)\'" \;
-- Rutger Nijlunsing ---------------------------------- eludias ed dse.nl never attribute to a conspiracy which can be explained by incompetence ---------------------------------------------------------------------- - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |