Ladislav Slezak schrieb:

On 5.10.2009 16:05, Stefan Schubert wrote:

...

Hi, I have documented how to handle translations in WebYaST:

http://en.opensuse.org/YaST/Web/Development/i18n

Thanks, I have two questions:

When a .po file is updated you have to call 'rake makemo', haven't you?

Yes you have.

What about adding this call to 'rake package' to ensure this call is not forgotten? Or is the person who integrates the translations back responsible for this and we should not take care of it?

The mo files will be generated while building the package in autobuild. So it make no sense to put it there. Perhaps it would make more sense to put it into "rake push". Josef ? :-)

Calling 'rake makemo' in system plugin prints the output twice, is that OK or is it a bug?

Thanks. That was a bug. I have fixed. Greetings Stefan -- To unsubscribe, e-mail: yast-devel+unsubscribe@opensuse.org For additional commands, e-mail: yast-devel+help@opensuse.org

Josef Reidinger schrieb:

Stefan Schubert write:

...

The mo files will be generated while building the package in autobuild. So it make no sense to put it there. Perhaps it would make more sense to put it into "rake push". Josef ? :-)

Hi, rake push is for testing that we don't break hudson before push and then push. What exactly is in this case tested? Broken string? Or somehow missing localization?

It reports for example old translations. The mo files will generated in autobuild too (It has the same level as compiling source code). So a check before checkin would make sense. Greetings Stefan -- To unsubscribe, e-mail: yast-devel+unsubscribe@opensuse.org For additional commands, e-mail: yast-devel+help@opensuse.org