From: Ingo Oeser <ingo.oeser@informatik.tu-chemnitz.de>
To: Richard J Moore <richardj_moore@uk.ibm.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [STATUS 2.5] July 10, 2002
Date: Sat, 13 Jul 2002 11:28:22 +0200 [thread overview]
Message-ID: <20020713112822.D758@nightmaster.csn.tu-chemnitz.de> (raw)
In-Reply-To: <OFECA8B235.6959642F-ON85256BF3.006A387F@portsmouth.uk.ibm.com>; from richardj_moore@uk.ibm.com on Thu, Jul 11, 2002 at 09:34:37PM +0100
On Thu, Jul 11, 2002 at 09:34:37PM +0100, Richard J Moore wrote:
>
> message uniqueness is not guaranteed
> message content is not complete for automation purposes
> some of the most serious error message have the least useful content
> many messages are issued using multiple printks and on an MP system can
> have their text interleaved
> there's no national language support
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^[1]
> embedded systems are not well catered for
> message recognition and parsing is haphazard
[1] Should stay like this. Or at least only the original message
should go to the log file.
Just an example:
Huch? Sytemkernseite konnte nicht an Adresse 1098bf00 eingeblendet werden.
current->tss.cr3 = 0062d000, %cr3 = 0062d000
*pde = 00000000
Huch: 0002
Prozessor: 0
EIP: 0010:[oops:_oops+16/3868]
EFLAGS: 00010212
eax: 315e97cc ebx: 003a6f80
ecx: 001be77b edx: 00237c0c
esi: 00000000 edi: bffffdb3
ebp: 00589f90 esp: 00589f8c
ds: 0018 es: 0018 fs: 002b
gs: 002b ss: 0018
Prozeß oops_test (pid: 3374,
Prozeßnummer: 21, Kellerseite=00589000)
Keller: 315e97cc 00589f98 0100b0b4 bffffed4 0012e38e 00240c64 003a6f80 00000001
This is only German, which is very similiar to whose character
set is a slight superset of the characterset in UK/US.
Now consider the same message in Chinese (20.000 possible
characters), Hebrew (right to left and 'strange' characters),
Arabic (right to left, strange rules for composing connections
between the characters, which even Micro$oft was unable to get
right) and many more fun.
So the driver writer has get his debugging messages translated
somehow and than he has to ask the translation serices again to
translate the bug report from the user.
Sorry, this sounds like someone is looking for a market niche
for getting more money instead of getting real problems solved.
Communication requires a common language. This is English for
Problems regarding Linux kernel development and maintenance.
Anything else would slow down both, because of added complexity.
Regards
Ingo Oeser, who thinks i18ned user space messages are enough
pain in the ass.
--
Science is what we can tell a computer. Art is everything else. --- D.E.Knuth
next prev parent reply other threads:[~2002-07-13 9:59 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-07-11 20:34 Richard J Moore
2002-07-13 9:28 ` Ingo Oeser [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-07-11 19:21 Richard J Moore
2002-07-10 18:08 Russ Weight
2002-07-10 17:46 Perches, Joe
2002-07-10 18:05 ` Thunder from the hill
2002-07-10 18:38 ` Alan Cox
2002-07-10 18:49 ` Kurt Garloff
2002-07-10 19:19 ` Larry Kessler
2002-07-10 21:15 ` Alan Cox
2002-07-11 18:07 ` Anton Blanchard
2002-07-10 21:27 ` Alan Cox
2002-07-10 5:11 Guillaume Boissiere
2002-07-10 15:49 ` Rik van Riel
2002-07-10 16:19 ` Adrian Bunk
2002-07-10 16:31 ` Thunder from the hill
2002-07-10 16:51 ` Roman Zippel
2002-07-10 17:00 ` Thunder from the hill
2002-07-10 16:54 ` Karim Yaghmour
2002-07-10 17:25 ` John Levon
2002-07-10 19:19 ` Karim Yaghmour
2002-07-10 17:17 ` Alan Cox
2002-07-10 20:21 ` Daniel Phillips
2002-07-10 17:12 ` Patrick Mochel
2002-07-10 17:42 ` Arnaldo Carvalho de Melo
2002-07-10 17:54 ` Robert Love
2002-07-10 19:18 ` Ville Herva
2002-07-10 20:03 ` Robert Love
2002-07-10 20:20 ` Cort Dougan
2002-07-10 20:25 ` Robert Love
2002-07-10 20:41 ` Ville Herva
2002-07-10 21:07 ` Alan Cox
2002-07-10 20:46 ` Robert Love
2002-07-11 9:46 ` Rogier Wolff
2002-07-10 20:26 ` Justin M. Forbes
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20020713112822.D758@nightmaster.csn.tu-chemnitz.de \
--to=ingo.oeser@informatik.tu-chemnitz.de \
--cc=linux-kernel@vger.kernel.org \
--cc=richardj_moore@uk.ibm.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®