* Tomohiro KUBOTA said: > Marek Habersack wrote: > > The only universal solution > > to all that I can see is to have a self-destroying script that would ask the > > user when s/he logins first what language to set up for him and then modify > > the appriopriate shell startup file. Sure, it's a dirty solution, but I > > can't think of any other at that moment :(( > > So far 'user-ja' supplies a 'user-ja-conf' command to establish the user's > personal Japanese environment. Also new preparing user-ja has a menu item > to invoke user-ja-conf. Your way can be a solution to make it easier. > Another is to have a file '/usr/local/sbin/adduser.local' but /usr/local > should not be used for Debian packages. As Michael pointed out in the other mail, another way would be to modify the startup scripts to check for a presence of some file in the user's directory and ask to setup the default language only if the file doesn't exist. Just a general idea. > Goswin Brederlow wrote: > > I\264m german but I certainly don\264t want my linux to talk german to me, > > same will be true for many polish users. Don\264t mess with their > > settings. > > Why? If > > (1) the admin is a Polish speaker and prefer Polish to English, That's the admin's personal preference. > (2) the admin is very sure all of the users of the machine are Polish > speaker and they prefer Polish to English, and > (3) no one use Polish-disabled console environment, Well, (3) is false for 99% of Polish users. I don't know about Japanese Windows (I know Japanese uses several coding systems, correct?), but Polish windows use completely non-standard (read: M$ Standard) coding and the ISO-8859-2 characters simply don't show up. And it's really hard to find ISO-8859-2 codings for Windoze (there are some, but they work rather bad). > then you can set LANG in /etc/environment, while I prefer to set it in > dot-files in the home directories for all users. If the admin prefer > English or s/he knows there are non-Polish-speaker user, the admin can > select not to set LANG. To force is bad but to offer selections is good. Exactly my point! Let the USER choose whatever s/he wants to use. Popup a menu or whatever the first time s/he logs in and let them choose. > > Then file a bug against the bootdisk to query the user for the > > language of his choise. Just changing it is evil and if random > > packages start poping up requests for language choise it will get > > anoing. > > I know this approach is preferable, straightforward, and beautiful. > But it is difficult to add 'Japanese' menu in the boot floppy because > > (a) it means we have to have one more floppy only for Japanese font, and > (b) I heard that 'kon2', a software to enable Japanese (and Korean > and Chinese with optional font files) to be displayed on console, > does not work for some machines. But most Japanese people can read the latin alphabet, correct? Is it also possible for the majority of your users to read the latin transcriptions of the Japanese language? If it is true, then it is possible to create a quasi-Japanese install. > If 'kon2' did not work well, boot floppy can use 'Ro-ma ji' expression, > that is, Japanese expressed in ASCII characters. (For example, 'KUBOTA' > is 'Ro-ma ji' expression of my name.) Oops :)) You just answered my question :)). Well then, perhaps the install process should use only the latin transcription? > But even if (a) and (b) are solved, boot floppy should not set > LANG variable for Japanese. It is because there are many environments > which cannot display Japanese such as Linux console, xterm, Eterm, Even with unicode? > are available in X, and so on so on. But I have not heard that any > Japanese distribution can use Japanese characters for file names (Of > course MS-Windows can do). Again, if you use Unicode, it's possible. > Piotr Roszatycki wrote: > > I'll submit a wishlist for boot-floppy. LANG variable should be set on > > first installation. > > (A) LANG selection should be independent on admin's preferable language. Yes. > (B) This selection should not be asked for CJK people or basic settings > for many softwares (input conversion engine, its interface to XIM, > emacs, kon2, and so on so on) should be done at the same time to > try to avoid side effects. Is it possible at all? > (C) This selection should be able to be modified or erased after > installation easily (with one command, if can). Yes, and possibly in a "blindfold" way should the console be rendered unreadable. marek
Attachment:
pgpVa6hg761eE.pgp
Description: PGP signature