RFC: [Horizon translation] string "%(action)s %(data_type)s"
Hi Horizon translators, I have a plan to make a small fix in Horizon strings in upstream code and if possible backport to Havana. Don't you have difficulties when translating a string "%(action)s %(data_type)s" in Horizon? It is used in two places: - to generate "action name" in the table (e.g. "Delete Network" in the pull-down menu and "Confirm Delete Network") - to generate "success message" (e.g. "Deleted Network: net2" in a success message pop-up) In Japanese we would like to use different translated strings for these strings (they are called "present" and "past" message respectively). Otherwise we can't get natural strings in translations. gettext has a mechanism called "message context", which allows us to translate a same string in different contexts. I have a plan to add a context to this string and allow us to use different translated words for the string. Once my fix is merged, we have the following entries in the PO file. The entries will become fuzzy, but we can reuse the existing translations so I believe the impact is small and we can get a benefit. Thought? Before proposing a patch, I would like to know feedbacks from I18N community. ---- #: tables/actions.py:562 #, python-format msgctxt "past" msgid "%(action)s %(data_type)s" msgstr "" #: tables/actions.py:564 #, python-format msgctxt "present" msgid "%(action)s %(data_type)s" msgstr "" --- Thanks, Akihiro Motoki <amotoki@gmail.com> / <motoki@da.jp.nec.com>
+1 :) 2013. 11. 19., 7:50, Akihiro Motoki <amotoki@gmail.com> 작성:
Hi Horizon translators,
I have a plan to make a small fix in Horizon strings in upstream code and if possible backport to Havana.
Don't you have difficulties when translating a string "%(action)s %(data_type)s" in Horizon? It is used in two places: - to generate "action name" in the table (e.g. "Delete Network" in the pull-down menu and "Confirm Delete Network") - to generate "success message" (e.g. "Deleted Network: net2" in a success message pop-up)
In Japanese we would like to use different translated strings for these strings (they are called "present" and "past" message respectively). Otherwise we can't get natural strings in translations.
gettext has a mechanism called "message context", which allows us to translate a same string in different contexts. I have a plan to add a context to this string and allow us to use different translated words for the string.
Once my fix is merged, we have the following entries in the PO file. The entries will become fuzzy, but we can reuse the existing translations so I believe the impact is small and we can get a benefit. Thought?
Before proposing a patch, I would like to know feedbacks from I18N community.
---- #: tables/actions.py:562 #, python-format msgctxt "past" msgid "%(action)s %(data_type)s" msgstr ""
#: tables/actions.py:564 #, python-format msgctxt "present" msgid "%(action)s %(data_type)s" msgstr "" ---
Thanks, Akihiro Motoki <amotoki@gmail.com> / <motoki@da.jp.nec.com>
_______________________________________________ Openstack-i18n mailing list Openstack-i18n@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-i18n
+1 If you have a code sample somewhere I'd like to check if it will fix some of the weirdness I get in the translated messages. Regards, -- Łukasz [DeeJay1] Jernaś On Mon, Nov 18, 2013 at 11:50 PM, Akihiro Motoki <amotoki@gmail.com> wrote:
Hi Horizon translators,
I have a plan to make a small fix in Horizon strings in upstream code and if possible backport to Havana.
Don't you have difficulties when translating a string "%(action)s %(data_type)s" in Horizon? It is used in two places: - to generate "action name" in the table (e.g. "Delete Network" in the pull-down menu and "Confirm Delete Network") - to generate "success message" (e.g. "Deleted Network: net2" in a success message pop-up)
In Japanese we would like to use different translated strings for these strings (they are called "present" and "past" message respectively). Otherwise we can't get natural strings in translations.
gettext has a mechanism called "message context", which allows us to translate a same string in different contexts. I have a plan to add a context to this string and allow us to use different translated words for the string.
Once my fix is merged, we have the following entries in the PO file. The entries will become fuzzy, but we can reuse the existing translations so I believe the impact is small and we can get a benefit. Thought?
Before proposing a patch, I would like to know feedbacks from I18N community.
---- #: tables/actions.py:562 #, python-format msgctxt "past" msgid "%(action)s %(data_type)s" msgstr ""
#: tables/actions.py:564 #, python-format msgctxt "present" msgid "%(action)s %(data_type)s" msgstr "" ---
Thanks, Akihiro Motoki <amotoki@gmail.com> / <motoki@da.jp.nec.com>
_______________________________________________ Openstack-i18n mailing list Openstack-i18n@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-i18n
Hi Lulasz, Please see https://bugs.launchpad.net/horizon/+bug/1252082 for the code changes. Thanks, Akihiro On Wed, Nov 20, 2013 at 5:35 PM, Łukasz Jernaś <deejay1@srem.org> wrote:
+1
If you have a code sample somewhere I'd like to check if it will fix some of the weirdness I get in the translated messages.
Regards, -- Łukasz [DeeJay1] Jernaś
On Mon, Nov 18, 2013 at 11:50 PM, Akihiro Motoki <amotoki@gmail.com> wrote:
Hi Horizon translators,
I have a plan to make a small fix in Horizon strings in upstream code and if possible backport to Havana.
Don't you have difficulties when translating a string "%(action)s %(data_type)s" in Horizon? It is used in two places: - to generate "action name" in the table (e.g. "Delete Network" in the pull-down menu and "Confirm Delete Network") - to generate "success message" (e.g. "Deleted Network: net2" in a success message pop-up)
In Japanese we would like to use different translated strings for these strings (they are called "present" and "past" message respectively). Otherwise we can't get natural strings in translations.
gettext has a mechanism called "message context", which allows us to translate a same string in different contexts. I have a plan to add a context to this string and allow us to use different translated words for the string.
Once my fix is merged, we have the following entries in the PO file. The entries will become fuzzy, but we can reuse the existing translations so I believe the impact is small and we can get a benefit. Thought?
Before proposing a patch, I would like to know feedbacks from I18N community.
---- #: tables/actions.py:562 #, python-format msgctxt "past" msgid "%(action)s %(data_type)s" msgstr ""
#: tables/actions.py:564 #, python-format msgctxt "present" msgid "%(action)s %(data_type)s" msgstr "" ---
Thanks, Akihiro Motoki <amotoki@gmail.com> / <motoki@da.jp.nec.com>
_______________________________________________ Openstack-i18n mailing list Openstack-i18n@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-i18n
participants (3)
-
Akihiro Motoki
-
Sungjin Kang
-
Łukasz Jernaś