On 15 October 2012 10:11, Jernej Simončič wrote:

On Mon, 15 Oct 2012 10:05:32 -0300, Joao S. O. Bueno wrote:

I've just comitted translations to Brazilian Portuguese there - but it ocurred me: Are the codes the same? he ISO translations code used elsewhere for my language is pt_BR -- will "pt_BR.setup.isl" work for the Windows part?

It doesn't matter what you name it as - I have to include the translation manually in the script file anyway. Of course, it helps if it's named after the language :)

Fine - now, about another bit:
it would be possible for me to create a Python script to to convert these files from and to
regular .po files - do you (all of you, not Jernej) think it could be worth it?

There would be many advantages to translators, one of which to be able to use one of the various tools suited for .po translation.

js ->

--
< Jernej Simončič ><><><><>< http://eternallybored.org/ >

_______________________________________________ gimp-user-list mailing list
gimp-user-list@gnome.org
https://mail.gnome.org/mailman/listinfo/gimp-user-list

On Mon, Oct 15, 2012 at 7:59 PM, Jernej Simončič wrote:

Sure, just remember that the output .isl files must be in the Windows ANSI encoding for that language.

By the way, should I use windows-1251/cp1251 code page for Russian?

Alexandre Prokoudine http://libregraphicsworld.org

On 15 October 2012 13:04, Alexandre Prokoudine wrote:

On Mon, Oct 15, 2012 at 7:59 PM, Jernej Simončič wrote:

Sure, just remember that the output .isl files must be in the Windows ANSI encoding for that language.

Eeek - - I just comitted today's translations in utf-8 -- do yopu confirm they should be in "cp1252" ("iso-8859-15") instead?

js ->

By the way, should I use windows-1251/cp1251 code page for Russian?

Alexandre Prokoudine http://libregraphicsworld.org
_______________________________________________ gimp-developer-list mailing list
gimp-developer-list@gnome.org
https://mail.gnome.org/mailman/listinfo/gimp-developer-list