-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512 On 01/10/14 18:04, Akihiro Motoki wrote: > Hi, > > 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). > > [Pros/Cons] (a) It is a simplest way as OpenStack upstream. > Packagers need to compile message catalogs and customize there > scripts. Deployers who install openstack from the source need to > compile them too. (b) It might be a simple approach from users > perspective. However to compile message catalogs during > installation, we need to install required modules (like babel or > django) before running installation (or require them as the first > citizen in setup.py "require"). I don't think it is much simpler > compared to option (a). (c1) Compiled message catalogs are a kind > of binary files and they can be generated from PO files. There is > no need to manage two same data. (c2) OpenStack is downloaded in > several ways (release tarballs is not the only option), so I don't > see much merits that the only tarball contains compiled message > catalogs. A merit is that compiled message catalogs are available > and there is no additional step users need to do. > > My preference is (a), but would like to know broader opinions > especially from packagers.
I'm for (a). There is no much sense in storing compiled catalogs in git. Just provide a setup.py command for us to invoke during build. I think it's ok for us to introduce new build time dependencies. /Ihar -----BEGIN PGP SIGNATURE----- Version: GnuPG/MacGPG2 v2.0.22 (Darwin) iQEcBAEBCgAGBQJULRUFAAoJEC5aWaUY1u57y7MH/iaEAKaRgaedVoEBcGwuxmHA yEO60pnIpGm6f2aD8zHc04jMDBXCLaarNdNoRP/D+5QSadrycnHNIrSWvvkb3V9+ TJqlv8JISU+zvA4gsstrk6qwu074TNyp/CI9gS6UjC9kKf65OW2ENERhCGT/pBur GGGXaryJJs07xtCD+H0Cg2xqntRx104CkUop9+queGG2by4IUgX8FhSRgq5YKmLj iTFl2FYZS8T+vdRgTYJrMq1KyZoPZhXfKM7I/4r8zqVXqJuglEgGzbgpzqqLHwjU J6qPNopVuNi+75wGLYtiQNXiv73plYjosyLuFPrcL2/trLS7CijBBdm+KtZUWwM= =dCGR -----END PGP SIGNATURE----- _______________________________________________ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
