Red Hat Bugzilla – Bug 120244
gdm missing ja translations because of overwriting jp.po
Last modified: 2007-11-30 17:07:01 EST
Description of problem:
This is bug 113995, which was fixed in FC1updates and Fc2devel,
but for RHEL3: basically because the spec file overwrites ja.po
with an older tweaked version various translations are missing
for ja (like "Password: ", "Shutdown", etc).
Version-Release number of selected component (if applicable):
Steps to Reproduce:
see bug 113995.
Notes: I recommend using the FC1updates srpm as the basis for this.
I've tested gdm-184.108.40.206-4 and it looks good. Thanks.
Actually it seems I was confused: for Taroon the overwriting of
the ja.po doesn't actually lose any translations or at least not
any really significant ones afaict - it was the missing "Shut_down"
that made me think there was a problem, but it turned out it is
missing upstream too.
However I noticed that the translation of "Username:" changed
to something slightly worse: so I'm sorry, but perhaps it is
better to undo the change.
I'll attach a patch for that below which should fix these problems.
Created attachment 99271 [details]
revert to overwriting ja.po and fix Shutdown ja
Jens: I should remove the perl hack now too, right?
i.e. these lines aren't relevant because gdm-ja.po has the correct
# fix the time format for ja
perl -pi -e 's|^msgstr "%a %b %d, %H:%M"|msgstr "%m/%d \(%a\)
perl -pi -e 's|^msgstr "%a %b %d, %I:%M %p"|msgstr "%m/%d \(%a\) %p
Yes, you're right: they won't do any harm, but might as well be
removed I suppose. Thanks. :-)
Okay, building this now.
I'll close this when the pkg has been moved to dist-3.0E-U2.
* Wed Apr 14 2004 Mark McLoughlin <email@example.com>
- Add back ja.po with a correct translation for "Shutdown" and remove
the perl date format foo (bug #120244)
An errata has been issued which should help the problem described in this bug report.
This report is therefore being closed with a resolution of ERRATA. For more information
on the solution and/or where to find the updated files, please follow the link below. You may reopen
this bug report if the solution does not work for you.