bofh@snoopy.virtual.net.au said:
> >> Let us assume that someone writes a very clever script analysing
> >> /ver/log/syslog and undertaking varius actions. You change language - it will
> >> be broken. (Like Internet Assistant for Polish and most other versions of MS
> >> Word (even the macro language there is in Polish ;-) )
>
> > I've been following this discussion, and it seems that the best approach
> >would be to have a new interface to klogd, that puts out '[nn]' prefixed
> >strings, followed by a default english interpretation. This way all
> >translating lookup can be done in user space...
>
> So you are suggesting having the kernel output both English error messages
> (suitable for straight dumping to /dev/console) and codes that klogd could use
> to load up strings in language files? I think that this idea would work.
> Klogd could then either pass on English strings or interpret the codes to
> another language, or it could just store the symbolic information to allow a
> log viewing program to view the logs in any language.
It should be possible to hash the English messages and translate them right
away. One would also want to replace the 'dmesg' utility with something that
translates the kernel message buffer as it is displayed (though this is
complicated by the variable numbers and such, it's feasible). Anyway, I think we
could get away with no control codes, which would require almost no kernel
rewrite (i.e., after booting, everything would be in Polish :)
--
_ ____ Joe Fouche (jf@ugcs.caltech.edu)
___| |--- Deranged College Student
--Zym1UcdkW86pzBZX
Content-Type: application/pgp-signature
-----BEGIN PGP SIGNATURE-----
Version: 2.6.3i
iQB5AwUBMuXUb3JgYOdk+W8JAQGM+AMgvdzrlI2eWp/6/SRoup7n//bQ1Yu9lOox
6sJ4hg1X112BfEHbIejKsgKs8Hjt3fagzgNE9DEw/4hI97YEa+RfVBqs7YALbC4q
cUw9AW/K0N6q05htRs1+/UVnTHCHazYMlpTpEA==
=sQBU
-----END PGP SIGNATURE-----
--Zym1UcdkW86pzBZX--