something I forgot to mention. I do not necessarily mean to discourage to translate CLI or server side messages. If we have enough resources to translate and review all of them, no problem. At now, most translators are volunteers and I hope our survey results help them choose materials they work on. Company-backed translators may have more time and have different criteria. I welcome them and would like to collaborate so that we can have consistent translation guidelines. Akihiro 2015-10-08 23:57 GMT+09:00 Akihiro Motoki <amotoki@gmail.com>:

Hi I18N team,

In the last moment in Liberty cycle, many translations of server side projects were incorporated. I think many language teams need to decide their priorities among various resources in the next release.

I would like to share the survey result on translated materials we made in Japan. We, Japanese community, made a rough survey on the interest in translated materials in OpenStack 5th birthday event in Japan (in July). It was done in a lightning talk and we roughly count the number of raised hands. We have >300 folks in the hall.

The question is very simple: Do you want or use translated version of the following or use English version?

The results are as follows. The numbers are percentage of interested folks.

- Horizon : 70~80% - Documentations : 40~50% (as long as they are kept up-to-date) - CLI : <5% (7~8 of >300) - Log messages : 0 (I could not find raised hands)

The following is my impression on priories in Japanese translations. - Horizon and documentations: should be prioritized. horizon first. - CLI: low priorities - log messages: Lowest priorities. - User visible messages from server projects: low priorities (though our survey didn't cover it). Note that it need to be prioritized if Horizon use these strings directly.

This is just my impression, and other languages must have different priorities.

Thanks, Akihiro