On Sat, Oct 30, 2010 at 4:18 PM, Denis Prost <denis.prost@wanadoo.fr> wrote:


Le 27/10/2010 09:31, Denis Prost a écrit :




Le 26/10/2010 18:30, Denis Prost a écrit :



Le 26/10/2010 17:51, Robert Xu a écrit :
On Tue, Oct 26, 2010 at 02:32, Denis Prost<denis.prost@wanadoo.fr>  wrote:

Le 25/10/2010 23:00, Robert Xu a écrit :
On Mon, Oct 25, 2010 at 15:37, Denis Prost<denis.prost@wanadoo.fr>    wrote:
Can the trinity developers take care of that ?

I think you should be able to compare with other po files and add it
yourself :P
I'll test for any breakage, if you desire.


I'm not sure I understand what you say. Do you mean adding new strings one
by one by hand in the po file ?
First, I might miss some new strings doing it that way.
Secondly, each trinity translater will have to do that manual strings adding
in his language po files. Seeing the number of languages trinity is
translated into, that seems to be a terrible waste of time.
A centralized process adding new strings to all po files in any languages
would be a lot more efficient. I can't imagine there's no automatic way to
achieve this. But unfortunately I don't know how and don't have much time to
investigate. I hope someone on the list has some knowledge about that topic.

hm, maybe Trinity could do something like Fedora does?
https://translate.fedoraproject.org

I can't tell myself, but surely a clear translation process providing all instructions needed would help.
(not forgetting that translators are just translators and may be very ignorant besides !).
Regards,

Denis

Maybe what we're looking for is here :
http://developer.kde.org/documentation/library/kdeqt/kde3arch/kde-i18n-howto.html#SECTION00050000000000000000
especially chapter 3 about Makefile.am.
As far as I understand (I just checked quickly) It seems that "make messages" should be run periodically on the source tree by its administrator to update the pot files, followed by some command to merge the new pot files with the existing corresponding po files for each language (at present time, the po files seem to exist only in kde-i18n directory as tarballs : maybe if they existed as untared in svn, it would be more easy to do the merging and then for the translators to update them.

Regards,

Denis
As long as there is no centralized process to update the po files, I'm trying to do it myself, but I don't know enough of the development tools to achieve it. Maybe someone might help me :
I'd like to run "make messages" in kdebase/kicker source directory, but there is no Makefile in it, only Makefile.am. How can I generate Makefile from it, what command should I run ?
Thanks,

Denis



If you downloaded the tarballs, you can (for most projects) use ./configure from the source directory for kdebase/kicker, that will do some checks for your dependencies and libraries on your specific system in order to generate a Makefile for your system. For svn, you generally need to follow a certain process to generate the configure script that will generate the Makefile. There are instructions in the Trinity Wiki in the Developers Web under How To Build: http://trinity.pearsoncomputing.net/wiki/bin/view/Developers/HowToBuild


--
Kris
"Piki"
Ark Linux Webmaster
Wannabe Ark Linux packager