Open Stack

Hi :-)

Korean terminology is out-of-date too.....

Need update! :-)

Thanks,
Sungjin Kang

2015-11-12 0:00 GMT+09:00 KATO Tomoyuki <tomo at dream.daynight.jp>:

> > On 11/11/2015 11:10 AM, Ying Chun Guo wrote:
> > > Hello, team
> > >
> > > I have submitted a patch to our repo for review, containing all the
> > > terminologies and translations we made.
> > > https://review.openstack.org/244031
> > > I want to discuss about how to handle these assets we made.
> > >
> > > Currently, I use a google doc to store the terms and the translations.
> > >
> https://docs.google.com/spreadsheets/d/1BRizUNhDLl_6NtsGconFkxsKUqAmEEGum9IcyurGdrQ/edit#gid=0
> > > I want to move these assets to our repo.
> > >
> > > My plan is to use pot and po files to store the terms and the
> translations.
> > > Then create a project named as "terminology" in Zanata, and
> > > create auto jobs to manage the synchronization between i18n repo and
> > > Zanata.
> > >
> > > So the process to update terms are:
> > > - If a people wants to add a new term to the terminology,
> > > submit a patch to i18n repo to change the original term.pot file.
> > > - If a people want to update a translation of a term,
> > > go to Zanata to update the translation.
> > >
> > > Let me know your thoughts to my design.
> > > Thank you.
> >
> > Zanato comes with its own glossary support which is AFAIU the same as
> > the terminology.
> >
> > Do you want to import the terminology as the Zanata glossary?
> > Or should the glossary be only handled directly in Zanata without the
> repo?
>
> In a short word, yes.
> We want to use them as the Zanata glossary, and translate them in Zanata.
> Also, we want to maintain them at i18n repo as an official resource.
>
> We are trying to create a tool that upload them to Zanata as the Zanata
> glossary.
>
> To keep track all work, we have a blueprint:
> https://blueprints.launchpad.net/openstack-i18n/+spec/translation-glossary
> (not approved yet :-)
>
> Thanks,
> KATO Tomoyuki
>
> _______________________________________________
> Openstack-i18n mailing list
> Openstack-i18n at lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-i18n
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-i18n/attachments/20151112/2e739911/attachment.html>