-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 07/10/14 18:00, Julie Pichon wrote:
I'm adding a couple of people on cc: with an interest in Ubuntu and
SUSE packaging: the Horizon team would love to have your opinion on
this (it came up during our weekly meeting).
The current consensus
On 08/10/14 20:51, James Page wrote:
On 07/10/14 18:00, Julie Pichon wrote:
I'm adding a couple of people on cc: with an interest in Ubuntu and
SUSE packaging: the Horizon team would love to have your opinion on
this (it came up during our weekly meeting).
The current consensus is leaning
Thanks James and Dirk,
First of all, sorry for moving this forward so late in the cycle.
I will remove mo files in Juno when importing the latest translations tomorrow.
On Wed, Oct 8, 2014 at 9:51 PM, James Page james.p...@ubuntu.com wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On
On 06/10/14 13:35, Ihar Hrachyshka wrote:
I was pointed (kudos to Alan Pevec) to the following update for RDO
spec file [1] that makes it regenerate MO files from source for Juno.
So for RDO, it's already handled the way we will probably go forward.
[1]:
I'm adding a couple of people on cc: with an interest in Ubuntu and SUSE
packaging: the Horizon team would love to have your opinion on this (it
came up during our weekly meeting).
The current consensus is leaning toward removing the mo files for Juno
RC2 (in a couple of days) rather than wait
Hi Julie,
I'm adding a couple of people on cc: with an interest in Ubuntu and SUSE
packaging: the Horizon team would love to have your opinion on this (it
came up during our weekly meeting).
I was somehow not CC'ed although I'm the SUSE packager for OpenStack.
In my opinion a) is the option
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On 04/10/14 18:12, Akihiro Motoki wrote:
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
Thanks Ihar, RDO already compiles message catalogs and nothing seems affected.
I also got an input from Debian maintainer (zigo) that it is a good
direction in Juno.
I would like to remove MO files (compiled message catalogs) in Juno
when importing translations this week.
Distributions have their
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
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
-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
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
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
13 matches
Mail list logo
