Open Stack

Thanks all for your input.
This topic was also discussed in the I18N team meeting this week.

All opinions I got so far are same and we seem to have a consensus.
- not to have mo files (compile message catalogs) in our source git repository.
- to provide a quick documentation on how to generate mo files and deploy them


This consensus raises another question. At now Horizon is the only
affected project.
Is it better to apply this consensus to Juno Horizon release or to
defer it to Kilo?
One concern is that most distributions have already prepared packages for Kilo,
so it might be better not to change now?
I would like to know opinions from distributors like RDO, Debian,
Ubuntu and so on.

Thanks,
Akihiro


On Thu, Oct 2, 2014 at 9:00 PM, Tom Fifield <tom at openstack.org> wrote:
> On 02/10/14 14:32, Łukasz Jernaś wrote:
>> On Wed, Oct 1, 2014 at 6:04 PM, Akihiro Motoki <amotoki at gmail.com> wrote:
>>> Hi,
>>
>> Hi Akihiro!
>>
>>> To display localized strings, we need to compile translated message
>>> catalogs (PO files) into compiled one (MO files).
>>> I would like to discuss and get a consensus who and when generate
>>> compiled message catalogs.
>>> Inputs from packagers are really appreciated.
>>>
>>> [The current status]
>>> * Horizon contains compile message catalogs in the git repo. (It is
>>> just a history and there seems no strong reason to have compiled one
>>> in the repo. There is a bug report on it.)
>>> * Other all projects do not contain compiled message catalogs and have
>>> only PO files.
>>>
>>> [Possible choices]
>>> I think there are several options. (there may be other options)
>>> (a) OpenStack does not distribute compiled message catalogs, and only
>>> provides a command (setup.py integration) to compile message catalogs.
>>> Deployers or distributors need to compile message catalogs.
>>> (b) Similar to (a), but compile message catalogs as a part of "pip install".
>>> (c) OpenStack distributes compiled message catalogs as a part of the release.
>>>     (c1) the git repo maintains compiled message catalogs.
>>>     (c2) only tarball contains compiled message catalogs
>>>
>>> Note that the current Horizon is (c1) and others are (a).
>>
>> I'd go for (a), as traditionally message catalogs were compiled during
>> the packaging step for Linux software (of course your experiences may
>> vary).
>> Of course if it was pretty straightforward to integrate it into pip
>> install it would also be a good solution.
>
> (a) sounds sane, but we should ensure that we tell the packagers that we
> expect them to make the compiled message catalogues so ops can more
> easily use the translations. (I guess this is like a modified version of
> (b))
>
> Regards,
>
> Tom
>
> _______________________________________________
> OpenStack-dev mailing list
> OpenStack-dev at lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev



-- 
Akihiro Motoki <amotoki at gmail.com>