PO files
This discussion is connected to the gimp-developer-list.gnome.org mailing list which is provided by the GIMP developers and not related to gimpusers.com.
This is a read-only list on gimpusers.com so this discussion thread is read-only, too.
PO files | Joao S. O. Bueno | 16 Sep 16:59 |
PO files | David Neary | 16 Sep 17:56 |
PO files | Sven Neumann | 16 Sep 18:11 |
PO files | Joao S. O. Bueno | 16 Sep 18:39 |
PO files | David Neary | 16 Sep 19:10 |
PO files | Daniel Egger | 16 Sep 21:53 |
PO files | Sven Neumann | 17 Sep 13:29 |
PO files | Daniel Egger | 17 Sep 14:30 |
PO files | Joao S. O. Bueno | 17 Sep 19:27 |
PO files | Sven Neumann | 16 Sep 18:08 |
PO files
Can someone point me to a "howto" or explaination on how are the files firstly generated?
I usually run everything in English here, but I was browsing the pt_BR.po, and it is looking a little worse than if the translations were done by an authomatic engine.
I'd guess no one at the connectiva team listed in the file is a GIMP user at all.
Regards,
JS ->
PO files
Joao S. O. Bueno wrote:
Can someone point me to a "howto" or explaination on how are the files firstly generated?
Sure. README.i18n contains the basics of how to use gettext.
The inaccurate Rough Guide is like this... you copy an existing po template file to one named after your localisation, translate the messages (being careful to use UTF-8), add the po files to CVS, and when you have po files for each of the localised directories (the dirs starting with po), add the language to ALL_LINGUAS in Makefile.am
The template files are .pot, and .mo files are the actual files used when localising - they're the hashmaps that map a message onto its localised version. Or something.
I usually run everything in English here, but I was browsing the pt_BR.po, and it is looking a little worse than if the translations were done by an authomatic engine.
If the language already exists, you can ignore the bits above, and just start translating the messages directly in pt_BR.po in the various directories, and the pt_BR.mos will be generated automatically when you make.
Cheers, Dave.
PO files
Hi,
"Joao S. O. Bueno" writes:
Can someone point me to a "howto" or explaination on how are the files firstly generated?
I usually run everything in English here, but I was browsing the pt_BR.po, and it is looking a little worse than if the translations were done by an authomatic engine.
Please read README.i18n as found in the toplevel directory of the GIMP source tree. If you have any questions not answered there, please feel free to ask here or on the gnome-i18n mailing list.
Sven
PO files
Hi,
David Neary writes:
Sure. README.i18n contains the basics of how to use gettext.
The inaccurate Rough Guide is like this... you copy an existing po template file to one named after your localisation, translate the messages (being careful to use UTF-8), add the po files to CVS, and when you have po files for each of the localised directories (the dirs starting with po), add the language to ALL_LINGUAS in Makefile.am
You missed an important point here: You should coordinate your translation effort with the GTP (GNOME Translation Project). Please do not start working on translations (new or existing ones) without getting in contact with the translation team for the particular language you are interested in.
Sven
PO files
On Tuesday 16 September 2003 1:11 pm, Sven Neumann wrote:
Hi,
David Neary writes:
Sure. README.i18n contains the basics of how to use gettext.
The inaccurate Rough Guide is like this... you copy an existing po template file to one named after your localisation, translate the messages (being careful to use UTF-8), add the po files to CVS, and when you have po files for each of the localised directories (the dirs starting with po), add the language to ALL_LINGUAS in Makefile.am
You missed an important point here: You should coordinate your translation effort with the GTP (GNOME Translation Project). Please do not start working on translations (new or existing ones) without getting in contact with the translation team for the particular language you are interested in.
Here goes what I got when writting the one in charge for pt_BR in the GTP pages:
Hi. This is the qmail-send program at conectiva.com.br.
I'm afraid I wasn't able to deliver your message to the following
addresses.
This is a permanent error; I've given up. Sorry it didn't work out.
--
:
Sorry, no mailbox here by that name. (#5.1.1)
--- Below this line is a copy of the message.
Return-Path: Received: (qmail 22270 invoked by uid 0); 16 Sep 2003 16:30:10 -0000 Received: from perninha.conectiva.com.br (200.250.58.156) by burns.conectiva with SMTP; 16 Sep 2003 16:30:10 -0000 Received: by perninha.conectiva.com.br (Postfix) id 1C23747432; Tue, 16 Sep 2003 13:35:04 -0300 (BRT) Delivered-To: godoy@conectiva.com.br ----------------------------------------
Does GTP have a list or something?
I think I have heard from this Godoy in a local free-software list, I
will check.
Meanwhile I've written the guy listed in the GIMP pt_BR file - that
mail did not seen to fail, and I will possibly get a reply.
Sven
_______________________________________________ Gimp-developer mailing list
Gimp-developer@lists.xcf.berkeley.edu http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-developer
PO files
Joao S. O. Bueno wrote:
Here goes what I got when writting the one in charge for pt_BR in the GTP pages:
Snip bounce
Does GTP have a list or something?
Hope this helps,
Dave.
PO files
Am Die, 2003-09-16 um 19.10 schrieb David Neary:
Is this the official new list for the GTP? If so README.i18n should be changed.
PO files
Hi,
Daniel Egger writes:
Is this the official new list for the GTP? If so README.i18n should be changed.
I might have missed something but what exactly do you think needs to be changed in README.i18n?
Sven
PO files
Am Mit, 2003-09-17 um 13.29 schrieb Sven Neumann:
Is this the official new list for the GTP? If so README.i18n should be changed.
I might have missed something but what exactly do you think needs to be changed in README.i18n?
I read in the thread that the GTP contact address is dead, if this is the case and it was mentioned in the README we should have changed it. However the broken address seems to come from somewhere else so this is a non-issue for us.
PO files
On Wednesday 17 September 2003 9:30 am, Daniel Egger wrote:
Re: [Gimp-developer] PO files
Date: Today 9:30:45 am
From: Daniel Egger
To: Sven Neumann
CC: gimp-developer@lists.xcf.berkeley.eduMessage was signed with unknown key. The validity of the signature cannot be verified. Problem: OpenPGP plug-in was not specified. Use the 'Settings->Configure KMail->Security' dialog to specify the plug-in or ask your system administrator to do that for you.
Am Mit, 2003-09-17 um 13.29 schrieb Sven Neumann:
Is this the official new list for the GTP? If so README.i18n should be changed.
I might have missed something but what exactly do you think needs to be changed in README.i18n?
I read in the thread that the GTP contact address is dead, if this is the case and it was mentioned in the README we should have changed it. However the broken address seems to come from somewhere else so this is a non-issue for us.
yes, a non issue.
The dead address was the e-mail for the pt_BR coordinator's e-mail. I
found his up to date e-mail in another free software related list
(and warned him that the GTP page should be updated).
I am now in touch with the guys at the pt_BR gtp team, and I will be able to help there with the Gimp.
JS ->