On Wed, 4 Dec 2002, Jim Z wrote: Jim,
This time, I hope my answer will solve your problem :-) > >From: Jungshik Shin <[EMAIL PROTECTED]> > >On Tue, 3 Dec 2002, Jim Z wrote: > > You can easily add 'Japanese(UTF-8' to your gdm/kdm language > >selection menu. See > ><https://bugzilla.mozilla.org/bugzilla/show_bug.cgi?id=75829> > I couldn't get into here and is it a typo? PLEASE help - I really want to I'm sorry it's <https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=75829> > > > I did a 'showmount -e 10.xxx.xxx.xxx' but I got scambled Japanese > > > characters for those entries that are encoded in UTF-8. Then I switched > >the > > > locale to ja_JP.UTF-8, but the same stuff was returned. What's wrong > >with > > > this picture? > It's an UNIX (Linux) to UNIX (NetBSD) mount. The UTF-8 Japanese file names > are in my NetBSD:/etc/exports. I can only mount those entries that are ASCII > equivalent. I also tried it from Solaris 8 (logged in as 'Japanese UTF-8 > (Unicode)') and it worked fine. I am sure if I can turn on UTF8 mode I > should be able to do so. NFS should be encoding-neutral just like the rest of Unix FS is. (except for cases like exporting to and from non-Unix systems where different file systems are used.). Why don't you begin with a simpler case? Before using UTF-8 for directory names to export via NFS, you can begin with making sure UTF-8 filenames under a NFS-exported directory come out all right on the client side. BTW, I've just experimented with UTF-8 directory names in export list(/etc/exports), it worked fine between Mandrake 9.0(server) and RedHat 8.0(client). Judging from this and the fact that Solaris and NetBSD worked fine, it should also work between NetBSD and RH 7.3 > > Needless to say, you have to run your shell in UTF-8 terminal > >(e.g. xterm 16x or mlterm) to view UTF-8 characters. > > > I can't get it to work. 'xterm -u8' doesn't work. the locale never changes. > From Solaris you can do a "LANG=ja_JP.UTF-8 dtterm &" and the new dtterm has You have to do the same for xterm as you do for dtterm. 'LANG=ja_JP.UTF-8 xterm'. '-u8' option is not necessary for recent xterm. Or, you can do in the opposite order. That is, run 'xterm -u8' and then set LANG to ja_JP.UTF-8 in xterm (UTF-8). Actually, you have to do the latter way if your /etc/sysconfig/i18n or ~/.i18n sets $LANG to a value other than ja_JP.UTF-8 because the shell initialization script in RedHat *overrides* the value set before the shell invocation with the value in /etc/sysconfig/i18n or ~/.i18n.(see /etc/profile.d/lang.(sh|csh)). > what is mlterm? Couldn't find it on Linux 7.3. I'm not sure if it's in RH 7.3. You can get it at http://mlterm.sourceforge.net Jungshik -- Linux-UTF8: i18n of Linux on all levels Archive: http://mail.nl.linux.org/linux-utf8/
