[Openstack-i18n] To language team coordinators: get ready for Mitaka translation
amotoki at gmail.com
Wed Mar 2 10:05:12 UTC 2016
Daisy and Tomo,
Thanks for dropping Japanese glossaries (+ follow-up).
We Japanese team are happy to re-join the standard way of I18n team
once we support contextual information.
It was not an easy choice, but from our discussion one-to-one mapping
from the source lang to Japanese does not work.
2016-03-01 22:45 GMT+09:00 Ying Chun Guo <guoyingc at cn.ibm.com>:
> Hi, KATO
> I have deleted Japanese glossaries.
> You can check now.
> Best regards
> Ying Chun Guo (Daisy)
> ----- Original message -----
> From: KATO Tomoyuki <tomo at dream.daynight.jp>
> To: Ying Chun Guo/China/IBM at IBMCN
> Cc: Openstack-i18n <openstack-i18n at lists.openstack.org>
> Subject: Re: [Openstack-i18n] To language team coordinators: get ready for
> Mitaka translation
> Date: Tue, Mar 1, 2016 7:21 PM
> Hi Daisy,
>> Thank you for the input, Akihiro and Kato.
>> I'm not strict in local communication method and IRC ID.
>> If you have clearly documented them in your team wiki, that's fine.
> Already enough clear in wiki,
> but only in Japanse :) because of local communication method.
>> As to the glossary, I still think git repository is better than
>> wiki to store glossaries. Git repo has strict control, while wiki
>> has no controls at all. Wiki is used for frequently update purpose.
>> After it turns to mature, Git repo is good to store.
>> And, using pot/po file can make all translation teams to easily follow the
>> same glossary list.
> Yeah, I myself am generally agree to managing glossary on git repository.
> But, as of now, it doesn't meet the requirements from Japanese team fully.
> We need a little more work.
>> I understand Japanese glossaries are out of date and your team don't
>> like the current one in Zanata. If that's your team decision, I'm OK
>> to delete it from Zanata.
> I think so. It's Japanese team dicision at now.
> KATO Tomoyuki
>> Best regards
>> Ying Chun Guo (Daisy)
> Openstack-i18n mailing list
> Openstack-i18n at lists.openstack.org
More information about the Openstack-i18n