> > i noticed a few bugs (?) in the installation process as well.
> > once apt starts up grading it does not care whether there is
> > a japanese displaying console on or not. it was not the case
> > on my machine and so i had mojibake on my screen during most
> > of the upgrade.
>
> Generally, it is users' responsibility not to set up Japanese
> locale under non-Japanese console. However, ~/.bashrc made by
> user-ja 0.28.potato.1 has the following lines
hehehe :-) the fact is that i did not set anything myself. if i remember well,
i read the upgrade english info included on the cdrom where of course nothing
is written about japanese locale (which does make sense). so i was extrememely
surpsised to see all the mojibake. the apt process being extremely
straightforward if you follow the instructions you absolutely have no worry.
only when the upgrade was over (or seemed to be) did i use user-ja-conf.
> > the .bashrc in user had problems with user-ja-conf (ver
> > 0.28 potato ?) : the modifications where writed over the
> > previous file in a place where is caused reading errors,
>
> Do you know the exact place which caused the error?
> What is the exact error message? (Though "reading errors"
> must be caused by bad permittion or broken disk, I think
> you are not saying about these problem.)
you are right. sorry i was not more explicit. it seems that user-ja writes
blocks of info starting with a #(beginning comments) line, intructions and
ending with a #(end comment). the beginning of the block in .bashrc was not
written on its own line but at the end of a line already present in the file.
the rest of the block was correctly inserted. the lines before that in .baschrc
were the alias section, and it seems the #(beginning comments) of the user-ja
conf were not considered as a comments since all the lines below (that include
the user-ja configuration) were considered as attempts at defining aliases. so
the messages i had on the screen after logging in were taking all the
configuration code lines one by one and saying that those were not aliases.
i tried to replace by hand the wrongly inserted #(beginning comment) line but
it did not seem to work so i copied the /root/.bashrc to /home/helary to get
everything straight.
> Sorry I don't have that Ohmsha book and I cannot help you
> with the disk1 problem. I hope someone who has the book
> or the author of the book reads this mailing list...
i asked on the french list and somebody told me i could force apt to accept any
name.
the solution i found to the name problem was to take the [install from a cdrom]
dselect option (not cdrom set). so i could install my packages cdrom by cdrom.
it was a long process because it seems that in this case dpkg checks _all_ the
packages on by one to see whether they were selected or not etc. so, even to
install only one package dpkg was running through the list of all the packages.
i noticed as well that nvi-canna had the same problems in 2.2 than in 2.1,
maybe user-ja does not work well with it or maybe it is another problem.
anyway, it does not seem to recognize the japanese input toggle. whatever i
typed (^k, ^o, ^\, ^@ etc, i tried pretty much all the keyboard) it did not
work. so anyway, i opted for jvim that works all right.
as far as japanese environment is concerned i would like to make the following
comments:
in the case of mc it seems that depending on whether a japanese display is on
or off i get the english version of mc or the japanese one. this is extremely
smart and helpful.
now, is there a way to emulate the same behavior for lynx and mutt for ex ? i
was not surprised to see my french mails with mojibake under mutt-ja but if
mutt-ja did not start my default and depended on the display method i could
start a second console and read japanese under one and french under the other.
same with lynx. i suppose the problem comes from lynx conflicting with lynx-ja
and mutt with mutt-ja. is there a way to overcome the conflicts and set up a
configuration depending on the display ? (ok, i suppose the answer is yes ;-)
another comment i have is the lack of knowledge of what is actually going on
during the upgrade, incl user-ja-conf. it would be so much easier to have a
file describing the changes to occur depending on the selected packages, and a
log of the modified files (although i suppose the instruction setting this log
must be trivial) and the way they were modified (or rather why they were
modified and in what section, something a human being can read without having
to totally understand the whole apt processes).
anyway, i suppose my upgrade is over, it took me about 15h to get things
working allright (to nights from 10 to 5 in the morning). my advice, start in
the morning and not during a week day :-)
now i would like to go back to my original post on japanese environment dvp. i
downloaded the ibm jdk and it looks like apt did not ask my authorization to
install all the c/c++ stuff so i am ready to start. except that, i have books
on java, python and perl but nothing on c. i browsed the whole oreilly
catalogue (and the japanese translations in my local bookstore) but i found
nothing like a 'learning c/c++' for total beginners. i _can't_ read a technical
book in japanese (the ohmsha book was ok because i knew what it was talking
about... more or less ;-) so i would appreciated reference either in english or
in french. i will order online if it is not too expansive, otherwise i'll make
do with online stuff if something is worth it. i am a very poor student, and i
accept book donations :-)
my orignal idea was to start a (not too complex) project from scratch to
understand what are the problems related to i18n/m17n on console. eventually a
small text editor. if it is too big a project for a beginner i accept
suggestions :-)
thank you for your help, past present and to come...
jc helary
ps:(i forgot to turn kon on so i write in english... sorry) there seem to be a
setonaikai linux user group, i subscribed to the list but it looks like there
is no traffic. i was thinking of organizing a udonkuu taikai in my 'hometown'
of takamatsu. anybody interested ?
