[OpenStack-I18n] Planning Barcelona Design Summit session - contributors meetup

Robert Simai robert.simai at suse.com
Mon Oct 17 07:40:08 UTC 2016

On Sunday 16 October 2016, 20:05:39 Andreas Jaeger <aj at suse.com> wrote:
> On 10/16/2016 01:41 PM, Akihiro Motoki wrote:
> > I think some of my added items might be aggressive, but my main point is
> > that the i18n team needs to express more focused areas to reduce
> > confusion around the feature freeze.
> > GUI message translation continuously gathers interest of translations so
> > far.
> > Documentation translation is the next one.
> > How about CLI? How about server project user-visible messages? How about
> > log messages?
> > This is my question.
> > 
> > According a rough survey I made in OpenStack Days Tokyo last year (one
> > year and a few months ago),
> > translation interest from the attendees was "Horizon > Documentation >>
> > CLI >> logging messages".
> > (there were no categories such as release notes and server user-visible
> > messages)
> Still, some translators translate log messages first, since they are
> nice and short ;(
> We can give translators more guidance on what to translate - or we can
> go one step further and disable some translations completely. Right now

No, please don't!

> if a project wants translation sync and sends a patch for
> project-config, it goes in. But does it make sense with current team to
> translate over 80 projects? Or should we instead tell projects: This is
> what we focus on, therefore let's only put these documents in Zanata -
> and nothing else?

To set the focus is fine - as already suggested, there could be pointers on 
the Zanata start page - but I don't see a reason to disallow lesser 
important translations. This will even block some language teams where the 
more relevant projects are already complete.


More information about the OpenStack-I18n mailing list