Note: tools/zanata/zanata_stats.py returns an error if
there is no "translators" section in a language in this yaml file.
Change-Id: I00d5a0ee0ec93e8f3856db2232c7c8d1e6d2b5cf
To be co-installable with other OpenStack projects and have consistent
testing it's a good idea (tm) to use constraints when creating tox
environments.
Change-Id: I776ac1ae0ef5067bc9679cad97a643ec8f852eb9
Currently the automatic translation imports link to
https://wiki.openstack.org/wiki/Translations/Infrastructure . That page
is inadequate now for reviewers. Let's write a new page targetting
reviewers of these imports and use that new page as reference.
Change-Id: I9b59e154d970a5667aee64e23e71ca3677c0026b
Document the current perecentages for message translation and the
policies used.
For background on the numbers, see
https://bugs.launchpad.net/horizon/+bug/1317794.
Change-Id: I796f71c73976c5acf42f8da92e87207bed1775b2
- Making consistent with
: https://review.openstack.org/#/c/380998/
- I would like to make use of Wiki to write and update
next meeting agenda.
Change-Id: Ic925a20c58f8591b2c47cfa20ef2e2e3e04e7d44
The translation check site is not available yet. It looks better to
improve the way to check Horizon translation using DevStack environment.
This commit also adds how to import latest translations
when DevStack is running.
Change-Id: I61b06aa09a62893d56b66ad9820f3d8cc958ac23
The names of OpenStack services are proper nouns, so "Comptue" in
"Compute service" and "compute" may be translated into different words.
I believe it is a good idea to add these service names.
"Telemetry" is renamed to "Telemetry service" as it seems to mean
OpenStack Telemetry service.
Change-Id: Iacb3ceaad3b4c8a9a58a7067576ab43f3169288e
There are various patterns of title headings at now.
It is better to unify the pattern of headings.
This commit adds the guideline.
Change-Id: I22563e6f480351762b22432ec6049b2ac5d8a2fe
update_catalog is used to update glossary PO files.
In glossary PO files, fuzzy matching proposes inappropriate entries
and as a result it is useless in most cases.
It looks reasonable to set no_fuzzy_matching to True in our use cases.
Change-Id: I3a77cb7ed231173fce27c666a9eed2821612d57c
Ian Y. Choi