Red Hat Bugzilla – Bug 196117
Wrong ja_JP translation for "refresh folder list"
Last modified: 2007-11-30 17:07:25 EST
The left-hand pane says "Check mail" instead of "refresh folder list" in the
Japanese version of Squirrelmail.
Patch from Hideshi Fuchi <email@example.com>
Created attachment 131256 [details]
The English text says "Check mail" here, so is it actually correct to have the
Japanese text say something different?
msgid "Check mail"
(the English language string)
(the current japanese translation)
Literally means "Check the mail"
(the proposed japanese translation)
ãªãã¬ãã·ã¥ (n,vs) refresh (e.g., memory); (P); EP
So is this really a bug?
I've checked my account run with squirrel-mail.
The translation of "Refresh" is more appropriate for this function named "Check
the mail" in English. Thus this translation is correct, please update with
An issue actually seems coming from the original English string.
"Check the mail" may cause confusion, and it would be better to change it to
"Refresh" to define it's functionality.
However I am not native English speaker but Japanese speaker, so the decision
should remain to you.
I am unable to view your png files, could you please provide URLs?
Created attachment 131712 [details]
screenshot showing the string "check the mail" in Japanese
Attached .png file.
Testing in FC with squirrelmail-1.4.7-2.
This request was evaluated by Red Hat Product Management for inclusion in a Red
Hat Enterprise Linux maintenance release. Product Management has requested
further review of this request by Red Hat Engineering, for potential
inclusion in a Red Hat Enterprise Linux Update release for currently deployed
products. This request is not yet committed for inclusion in an Update
This is working properly. This patch changes the string in the top left within
An advisory 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.