> Teunis Peters (teunis@usa.net) writes:
> > I _REALLY_ wish this could be in the kernel - BUT due to translations (Yet
> > Another Unicode Filesystem) this is a 'can't happen'. I _REALLY_ gotta
> > finish that UTF-8 code [hopefully this weekend] - work been too busy.
>
> There is UTF-8 support already in this code. Currently, you need to
> use a mount option utf8 to use it, but it should work just fine. I don't
> see any reason it won't go in. I've only sent it to Linus once, and that
> was just before the filesystem changes began, so it really hasn't had
> much of a chance yet.
Alright! But is it in a generic layer so all kernel-components can use
it? [and can you remove the codepage et al support? Or at least make it
disableable? That's the biggest complaint...]
I see... it can :) But it would still be best left to userspace to handle
this... This driver (0.3.9) has been much cleaned up :)
Can it default to:
UTF-8 enabled (from UCS-2 [Windows/Unicode 1.0] and UCS-4 [Unicode2.0]
NONE of the page-translations loaded.... so no kernel bloat :)
Let me know (personal email or something) when the new driver is
available! [I have Joliet CDs thanks to W95 being used to backup my
system by a friend]
I vote it for 'testing kernel' - it'd make transfering data from other
os's (or wannabes like W95) a lot easier :) Not all systems have the
enlightenment of Linux to actually follow data exchange standards...
G'day, eh?
- Teunis