The recommended way to do the translations is via the PO files (there's
only one for each language), which are then turned into LMO by a script
(don't worry about this part).
To do it for pt-br:
1) go to
https://github.com/libremesh/lime-packages/tree/develop/packages/lime-webui…
2) copy the "es" folder and its contents, and rename the folder to
"pt-br"
3) edit the msgstr lines to your satisfaction, either with a text
editor, or with a specialized translation app, such as
http://www.poedit.net/
4) commit and submit a pull request
This way you only deal with one file -- when the script is run it pulls
out all the translatable strings for you, so you don't have to search
for them. If you've already translated some LMO files, then maybe you
can run the script and see if it does steps 1 and 2 (below) for you, and
let us know what happens.
Rodrigo in Brazil also wanted to help with translation.
At some point we might have another interface for doing the translation,
but for now this way seems to work.
~ Patrick
On 01/26/2018 06:03 AM, Nicolas Pace wrote:
Hi Henrique,
On Sat, 2018-01-13 at 20:38 +0000, Henrique Mohr wrote:
Hello all! I was doing some translations on .lua
files (or hard
translations if you so) to pt-br. And then i realized that lime has
translations for ENG and ESP in some files with .lmo extension.
I saw where the code generates its .lmo files but
idk how to proceed.
As I understand, Patrick Gibbs (that is part of the list) is working on
a streamlined process to translate all the content (the software, but
also the site, the companion apps, ...).
For now, you can edit the .lmo and send a pull request!
>
>
> Any effort on that way?
>
>
> Henrique
> _______________________________________________
> lime-users mailing list
> lime-users(a)lists.libremesh.org
>
https://lists.libremesh.org/mailman/listinfo/lime-users
>
>
> _______________________________________________
> lime-users mailing list
> lime-users(a)lists.libremesh.org
>
https://lists.libremesh.org/mailman/listinfo/lime-users