| |||||||||||||
|
| |||||||||||||
Why use translation?Why use translation?Posted Apr 18, 2003 17:05 UTC (Fri) by melauer (guest, #2438)Parent article: Time to internationalize the kernel? Isn't the text of a kernel message, or the constant part of it (i.e. minus any variables such as device names), just as unique as a number assigned to the message would be? If so, then perhaps the text of the kernel message itself could be the index to a translation database, just like the index number suggested by Mr. Williams. You would need more than a basic pattern matcher to match those kernel messages which include device names, path names, or any other variables, but that should be doable. The only problem with this method that I can think of would be if the text of kernel messages changed too much, causing the error message database to need constant updating. Even then, any given distro should be able to create an error message database for their official kernels. Once the database is created for one kernel, they only need to update it for each new kernel release, and these occur infrequently.
(Log in to post comments)
Why use translation? Posted Apr 18, 2003 17:36 UTC (Fri) by melauer (guest, #2438) [Link] I hate to reply to myself, but there's something I should have mentioned.Although the article mentions massive numbers of kernel error messages being "affected" in recent kernels, I'm not convinced that this means that the text of kernel messages changes regularly. Even if "affected" means that text was changed, remember that there was a lot of patching related to cleaning up spelling/grammatical errors in the kernel recently (The sort of thing probably won't happen again anytime soon). I'll have look at those patches when I have the time to see what exactly went on. In the meantime, I'm still not convinced that kernel error messages change so much from patch to patch.
|
|
||||||||||||