2010/11/6 KAMI911 KAMI911
> Hi!
>
> It is not easy to steamlined the extension that comes from outside
> (downloadable oxt). Maybe we can put po files to Pootle then the
> translators
> can can do their tasks easily. We can convert it back to properties file
> and
> send it to the developer or di
Hi!
It is not easy to steamlined the extension that comes from outside
(downloadable oxt). Maybe we can put po files to Pootle then the translators
can can do their tasks easily. We can convert it back to properties file and
send it to the developer or directly inject to the oxt (zip files).
Rega
Great!
Isn't that the point of localization - that the product is fully localized?
It is just that te process must be simplified and centralised in some way to
be transparent and manageable.
Lp, m.
2010/11/6 Kálmán „KAMI” Szalai
> Dear Translator Commnity,
>
> Are you interested to translate e
Dear Translator Commnity,
Are you interested to translate extensions that could be enabled via
LibO build environment? I created a workflow to convert properties files
to po then back. Lets discuss the possibilities and if you are commited
to translate such extensions I will publis scripts, and th
Hi Rimas,
El dv 05 de 11 de 2010 a les 21:51 +0200, en/na Rimas Kudelis va
escriure:
>
> Try to adapt the solution from here:
> http://www.mail-archive.com/debian-u...@lists.debian.org/msg477907.html
>
> It didn't seem to work for me though, but I remember there was a time
> when Russian was s
