Do you want we have out-of-date Japanese glossary in i18n repo? I am not a fan of this but am okay if you want. 2016-03-02 22:05 GMT+09:00 Ying Chun Guo <guoyingc@cn.ibm.com>:

I hope you can agree to abandon it. We can work on the improvement after the po format for new glossary feature is clear.

Best regards Ying Chun Guo (Daisy)

Akihiro Motoki <amotoki@gmail.com> wrote on 03/02/2016 09:01:12 PM:

...

From: Akihiro Motoki <amotoki@gmail.com> To: Ying Chun Guo/China/IBM@IBMCN Cc: Tomoyuki KATO <tomo@dream.daynight.jp>, "openstack- i18n@lists.openstack.org" <openstack-i18n@lists.openstack.org> Date: 03/02/2016 09:02 PM Subject: Re: [Openstack-i18n] To language team coordinators: get ready for Mitaka translation

Daisy,

What should I do for https://review.openstack.org/285725 ? Should abandon it?

2016-03-02 19:05 GMT+09:00 Akihiro Motoki <amotoki@gmail.com>:

...

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.

Akihiro

2016-03-01 22:45 GMT+09:00 Ying Chun Guo <guoyingc@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@dream.daynight.jp> To: Ying Chun Guo/China/IBM@IBMCN Cc: Openstack-i18n <openstack-i18n@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.

Thanks, KATO Tomoyuki

...

Thoughts?

Best regards Ying Chun Guo (Daisy)

_______________________________________________ Openstack-i18n mailing list Openstack-i18n@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-i18n