[Openstack-i18n] OpenStack interface in Indian languages
amotoki at gmail.com
Thu Feb 26 13:53:46 UTC 2015
The topic fits openstack-i18n ML.
I hope you replied not just to Tom but also openstack-i18n list :-)
It sounds great to coordinate efforts of all Indian languages.
There are a lot of languages in India and I know coordinating all
efforts is not easy.
Tom already gave a lot of information, but I would like to add some information
to your questions even if there are some duplications.
> 1) Which Indian language translations are already been contributed to
> OpenStack by other contributors.
https://wiki.openstack.org/wiki/I18nTeam does not cover all languages.
It is just maintained by an voluntary effort of all translators aware
of the page.
We currently use Transifex as the translation interface.
If you see a translators or language coordinator who is active in Transifex
you can reach him/her by Transifex interface.
Previously I found Japanese translator who is very active in Transifex but
I didn't know his contact and I reached him through Transifex
and now we are both coordinating Japanese translations.
> 2) Where do we get information about all the language Maintainers/
Tom's reply already covers well.
If a language coordinator is not active, the maintainers of OpenStack
In the new interface of Transifex, it is not easy to know who are the
OpenStack project team. The best way to ask it in openstack-i18n ML.
Most active translators/maintainers are reading the list.
> 3) What are the priority areas for translations. For example one needs
> to know which files needs to be translated first and from where do we
> get these files.
Horizon and several documentations are the priority areas.
In most active languages, it seems Horizon has the priority because it
is the interface
end users face. I believe there is no doubt that Horizon is the first priority.
For documentation translation, each language team decides their
priority team by team.
On the other hand, there are some discussions on setting prioritities
on some documentations
in openstack-i18n meeting. If you would like to provide translations
for all Indian languages
to some same level, it might be better to define which documentations
so that translators can work on same documents.
> 4) Which are the platforms for contributing the strings etc.
As you may know, we are using Transifex now.
All translations available on Transifex are imported into OpenStack repository
by periodic jobs. For stable branches, the import are done manually.
2015-02-26 22:23 GMT+09:00 Tom Fifield <tom at openstack.org>:
> Thanks for the rapid reply!
> As you're probably aware, we use Transifex to manage translation for
> Source strings are automatically uploaded to Transifex when the code
> changes, and new Translated strings are automatically downloaded to the
> code repository when they are updated on Transifex.
> For the Horizon dashboard, which is the primary user interface
> translation, you can see all languages and their progress at:
> Here is the status for each Indian language at present. For
> convenvenience I'll divide them into 3 types:
> A) Some translations exist:
> Hindi - 84% - https://wiki.openstack.org/wiki/I18nTeam/hi
> Nepali - 10% - Surit Aryal <surit.killer at gmail.com>
> Punjabi - 7% - https://wiki.openstack.org/wiki/I18nTeam/pa_IN
> Telugu - 4% - Thirunahari Dyvik Chenna <dyvik100 at gmail.com>
> Marathi - 1% - Swapnil S Kulkarni <coolsvap at gmail.com>
> Oriya - 1%
> As these teams are somewhat active, consider contacting the organisers
> using the above details to let them know your intentions. Ask them
> whether they'd consider sharing coordination duties. They'll probably
> agree, so when that happens, let us know and we can assign the
> coordinator role. You will likely also want to update the wiki page:
> B) Team exists on Transifex, but no translations so far:
> As these are not active, get the person you want to be the coordinator
> for join the language on https://www.transifex.net/projects/p/openstack/
> then effectively follow this process:
> https://wiki.openstack.org/wiki/I18nTeam/CreateLocalTeam - you won't
> need to add the language
> C) Not currently translated:
> As these are not active, get the person you want to be the coordinator
> for each language and follow this process:
> https://wiki.openstack.org/wiki/I18nTeam/CreateLocalTeam - you will need
> to click "Add Language"
> Now, in terms of practical translation aspects, I am going to assume
> that you will first want to work on the Horizon Dashboard, as it is the
> highest translation priority and most visible/rewarding component to do.
> There are 30 other OpenStack projects that are translated, including
> documentation, but for simplicities sake I'm going to ignore them for now :)
> So, if we click through to Hindi from our earlier 'Horizon' page, we get:
> On here the first very important thing is that there are a number of
> resources. They include the version of the release: Icehouse, Juno, Kilo
> etc. There are three different resources under Kilo ("Horizon
> Translations, OpenStack Dashboard Translations and Java Script
> Translations") and each of these need to be translated for the whole
> dashboard to be complete.
> My recommendation would be to focus only Kilo resources and ignore the
> Icehouse/Juno resources. Kilo is the next release that will be
> announced, on April 30th 2015.
> If you are logged in to Transifex as a member of the Hindi translation
> team, clicking on "Kilo - OpenStack Dashboard Translations" will bring
> up a window where you can start translating.
> Here, you have two options.
> 1. Click "Translate Now" and use the web interface (your translations
> will go directly into transifex)
> 2. Click "Download for Use" and use the PoT file directly (you will need
> to upload the file once it is translated).
> Unless you already are familiar with using PoT files, or have an
> unreliable internet connection, I would recommend using the Transifex
> web interface. It has a few strong advantages:
> * multiple translators can work at the same time
> * strings will be automatically saved in transifex, no upload step
> * in-built translation memory and glossary
> I hope this has answered some of your questions! Please have a play
> around on Transifex and see what you think. The interface is fairly
> intuitive, but can occasionally be confusing.
> We're here for questions as required! Looking forward very much to
> working together.
> On 26/02/15 20:44, chandrakant dhutadmal wrote:
>> Hi Tom.
>> Thanks for responding to the email. I want to understand following things.
>> 1) Which Indian language translations are already been contributed to
>> OpenStack by other contributors.
>> 2) Where do we get information about all the language Maintainers/
>> 3) What are the priority areas for translations. For example one needs
>> to know which files needs to be translated first and from where do we
>> get these files.
>> 4) Which are the platforms for contributing the strings etc.
>> We have already undertaken to translate attached files. So we need
>> further clarification on whether we are going the right way ?
>> Chandrakant Dhutadmal.
>> On Thursday, February 26, 2015 3:17 PM, Tom Fifield <tom at openstack.org>
>> On 18/02/15 15:13, chandrakant dhutadmal wrote:
>>> Hi All.
>>> It gives me great pleasure in informing you all that C-DAC, Pune (Centre
>>> for development of advanced computing) has decided to contribute in
>>> translating OpenStack interface in all 22 Scheduled Indian languages.
>>> @Chandan Kumar has been helpful in getting started.
>>> Need to discuss this with language team leaders/ maintainers in order to
>>> avoid duplicate efforts. Please comment.
>> This sounds excellent. What help do you need?
>> Openstack-i18n mailing list
>> Openstack-i18n at lists.openstack.org
>> <mailto:Openstack-i18n at lists.openstack.org>
> Openstack-i18n mailing list
> Openstack-i18n at lists.openstack.org
Akihiro Motoki <amotoki at gmail.com>
More information about the Openstack-i18n