Red Hat Bugzilla – Bug 14496
[text-install] Clock testing warning message not translated
Last modified: 2008-05-01 11:37:56 EDT
This message, displayed before clock chip testing in text install, isn't
"It is possible that the hardware detection routines in the server somehow
cause the system to crash and the screen to remain blank. If this is the
case, skip this step the next time. The server may need a RamDac, ClockChip
or special option (e.g. "nolinear" for S3) to probe and startup correctly."
This would be an Xconfigurator bug.
Which language? This string is marked for translation.
Not a bug... if you want to help out with translation, ask for the po file from
the translation robot. For more information, contact Dale (firstname.lastname@example.org)
I'm sorry for leaving that info out; the install was done in Swedish.
The message is in the Swedish Xconfigurator po file and has been so since
February (I just double-checked with the robot):
"It is possible that the hardware detection routines in the server some how "
"cause the system to crash and the screen to remain blank. If this is the "
"case, skip this step the next time. The server may need a Ramdac, ClockChip "
"or special option (e.g. \"nolinear\" for S3) to probe and start-up correctly."
"Det dr mvjligt att herdvarudetekteringsrutinen i servern pe negot sdtt "
"orsakar att systemet kraschar och att skdrmen fvrblir blank. Om detta "
"intrdffar bvr du hoppa vver detta steg ndsta geng. Servern kan behvva en "
"RAMDAC-instdllning, klockkretsinstdllning eller en speciell flagga "
"(exempelvis \"nolinear\" fvr S3) fvr att kunna testas och startas korrekt."
And, yes, I'm the Swedish translator.
Please try the newest packages from http://people.redhat.com/~teg/xc/
If these doesn't help, try beta5 - glibc has had some i18n changes lately.
Update status after that.
Oh - the package looked fully translated when I tried it, no English text
anywhere. This exact screen didn't show up, though.
Does it work now, with pinstripe or the 4.3.37 (or higher) at
I'll assume it's fixed - if it's not, reopen (that way, I would get some