[yast-devel] Proofreading YaST Messages
In an heroic way, Martina Dejmek proofread many (new) YasT messages the last days. Internally, find the results in my export directory as .../10.3/proofed-2007-08-23.tar.gz . Maybe, I should create a bug report an attach it. Two notes ========= 1/ Do *not* apply these corrections now. Remember, string freeze is effective since quite some time. 2/ We will use the corrections as "overloads". This means, we will install them as en_US translations. So, if you receive a bug report with an unknown message quoted, check the en_US .mo file using msgunfmt and use the msgid for grepping thru your sources. If any "translation" does not match you expection, talk to me and Martina. We will happily adjust the en_US files for something better. Let me repeat with other words, we did not touch the messages already approved by the previous proofreader. But considerably more than 2000 messages were in an unchecked state in the meantime and Martina worked on those only. For the record, Jana proofread several important modules completely some days ago. Jana's findings, together with remarks by Benji, already made it into the source code. I'm rather happy that we reached this goal now! Karl -- Karl Eichwalder R&D / Documentation SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nuernberg) -- To unsubscribe, e-mail: yast-devel+unsubscribe@opensuse.org For additional commands, e-mail: yast-devel+help@opensuse.org
participants (1)
-
Karl Eichwalder