On 02/10/14 14:32, Łukasz Jernaś wrote:
> On Wed, Oct 1, 2014 at 6:04 PM, Akihiro Motoki <amot...@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



OpenStack-dev mailing list

Reply via email to