Hi all, ************************************************************************************* PLEASE CHECK YOUR TRANSLATIONS OF THE FOLLOWING STRINGS ************************************************************************************* The issue that a couple of wrong source strings are displayed I reported yesterday has been fixed. However the wrong strings are just substituted by the correct strings and they are never marked as fuzzy or untranslated. You must have wrong translations corresponding to the wrong source strings. Some wrong source strings are completely different from the correct ones. Please make sure to check your translations for strings in the following list. /FYI/ Texts in parentheses are the wrong source strings. == Horizon Translations == * Limit Summary (<-- Summary) * Instances (<-- Instance) * Select a period of time to query its usage (<-- Select a month to query its usage) * This Period's VCPU-Hours (<-- This Month's VCPU-Hours) * This Period's GB-Hours (<-- This Month's GB-Hours) == OpenStack Dashboard Translations == * All Projects (<-- Projects) * Project Groups (<-- Projects) * Not Found (<-- Page Not Found) * Policy (<-- Polish) * Policies (<-- Polish) * Project Limits (<-- Projects) * Connection Limit: (<-- Projects) * VPN Connections (<-- Projects) Thanks, Akihiro On Tue, Sep 17, 2013 at 7:35 PM, Akihiro Motoki <amotoki@gmail.com> wrote:
Hi all,
Woops, I forgot to report the progress. Daisy and I confirmed my patch solves the problem before I proposed the patch. Once the patch is merge, the strange issue will be addressed. Temporary you can see the strange source string fixed because of our tests.
There are many I18N related fixes proposed in Horizon. Thanks all for your feedback!!! We need to review the status of those patches in today/tomorrow's Horizon meeting. I hope you add a tag 'i18n' when you report a bug related to traslation work in Horizon launchpad.
Regards, Akihiro
On Tue, Sep 17, 2013 at 5:54 PM, Julie Pichon <jpichon@redhat.com> wrote:
"Ying Chun Guo" <guoyingc@cn.ibm.com> wrote:
It's strange.
I think we may need to remove "fuzzy" from the source file "en.po" and update Transifex. We also need to find a option setting to avoid the fuzzy matching while generating messages.
Unfortunately it's not possible to force Django not to provide fuzzy translations, see [0].
I'm hoping that Akihiro's patch (thanks!) will resolve the problem by removing all existing 'en' translations (so there shouldn't be anything to fuzzy-match against).
Regards,
Julie
[0] https://code.djangoproject.com/ticket/10852
In "en.po":
#: templates/horizon/common/_usage_summary.html:5 #, fuzzy msgid "Select a period of time to query its usage" msgstr "Select a month to query its usage"
Regards Ying Chun Guo (Daisy)
-- Akihiro MOTOKI <amotoki@gmail.com>
-- Akihiro MOTOKI <amotoki@gmail.com>