Hi everyone,
this is my first post to the list. I proposed myself to translate new strings into french and Tim advised me to post here my questions. I know how to use kbabel or poedit, but that's about all. I would need someone to tell me what are the steps to follow to : 1) get po files updated with new strings corresponding to the added features since 3.5.10 2) update these po files in the source tree, once I've added the translated strings into them Thanks for any help, regards,
Denis
Hi everyone,
no answer, so I'm trying to find my way myself to translation process ! I tried to start with :
svn import /home/denis/Bureau/trinity http://websvn.kde.org/branches/trinity/ -m nomsg --non-interactive
but got an error message :
svn: Repository moved permanently to '/branches/trinity/'; please relocate
I'm really new to svn, can anyone help me to find out what's happening ?
Thanks,
Denis
Le 11/10/2010 17:13, Denis Prost a écrit :
Hi everyone,
this is my first post to the list. I proposed myself to translate new strings into french and Tim advised me to post here my questions. I know how to use kbabel or poedit, but that's about all. I would need someone to tell me what are the steps to follow to :
- get po files updated with new strings corresponding to the added
features since 3.5.10 2) update these po files in the source tree, once I've added the translated strings into them Thanks for any help, regards,
Denis
Hi everyone,
Still no answer, nobody can help me ? the only thing I need is updated po files for trinity 3.5.12, so that I can translate the new strings. Regards,
Denis
Le 17/10/2010 15:19, Denis Prost a écrit :
Hi everyone,
no answer, so I'm trying to find my way myself to translation process ! I tried to start with :
svn import /home/denis/Bureau/trinity http://websvn.kde.org/branches/trinity/ -m nomsg --non-interactive
but got an error message :
svn: Repository moved permanently to '/branches/trinity/'; please relocate
I'm really new to svn, can anyone help me to find out what's happening ?
Thanks,
Denis
Le 11/10/2010 17:13, Denis Prost a écrit :
Hi everyone,
this is my first post to the list. I proposed myself to translate new strings into french and Tim advised me to post here my questions. I know how to use kbabel or poedit, but that's about all. I would need someone to tell me what are the steps to follow to :
- get po files updated with new strings corresponding to the added
features since 3.5.10 2) update these po files in the source tree, once I've added the translated strings into them Thanks for any help, regards,
Denis
On Mon, Oct 25, 2010 at 1:44 AM, Denis Prost denis.prost@wanadoo.fr wrote:
Hi everyone,
Still no answer, nobody can help me ? the only thing I need is updated po files for trinity 3.5.12, so that I can translate the new strings. Regards,
Denis
Le 17/10/2010 15:19, Denis Prost a écrit :
Hi everyone,
no answer, so I'm trying to find my way myself to translation process ! I tried to start with :
svn import /home/denis/Bureau/trinity http://websvn.kde.org/branches/trinity/ -m nomsg --non-interactive
but got an error message :
svn: Repository moved permanently to '/branches/trinity/'; please relocate
I'm really new to svn, can anyone help me to find out what's happening ?
Thanks,
Denis
Le 11/10/2010 17:13, Denis Prost a écrit :
Hi everyone,
this is my first post to the list. I proposed myself to translate new strings into french and Tim advised me to post here my questions. I know how to use kbabel or poedit, but that's about all. I would need someone to tell me what are the steps to follow to :
- get po files updated with new strings corresponding to the added
features since 3.5.10 2) update these po files in the source tree, once I've added the translated strings into them Thanks for any help, regards,
Denis
I think you should keep persisting. Translations are going to be needed.
Unfortunately I only know English, so I can't help. But keep persisting, someone will help.
Le 25/10/2010 07:52, Kristopher Gamrat a écrit :
I think you should keep persisting. Translations are going to be needed. Unfortunately I only know English, so I can't help. But keep persisting, someone will help.
Thanks for your encouragement, Kris, I'll do !
Denis
Sorry, I missed this one : http://trinity.pearsoncomputing.net/wiki/bin/view/Developers/HowToBuild It seems that there is eveything I need to start here. Regards,
Denis
Le 25/10/2010 07:44, Denis Prost a écrit :
Hi everyone,
Still no answer, nobody can help me ? the only thing I need is updated po files for trinity 3.5.12, so that I can translate the new strings. Regards,
Denis
Le 17/10/2010 15:19, Denis Prost a écrit :
Hi everyone,
no answer, so I'm trying to find my way myself to translation process ! I tried to start with :
svn import /home/denis/Bureau/trinity http://websvn.kde.org/branches/trinity/ -m nomsg --non-interactive
but got an error message :
svn: Repository moved permanently to '/branches/trinity/'; please relocate
I'm really new to svn, can anyone help me to find out what's happening ?
Thanks,
Denis
Le 11/10/2010 17:13, Denis Prost a écrit :
Hi everyone,
this is my first post to the list. I proposed myself to translate new strings into french and Tim advised me to post here my questions. I know how to use kbabel or poedit, but that's about all. I would need someone to tell me what are the steps to follow to :
- get po files updated with new strings corresponding to the added
features since 3.5.10 2) update these po files in the source tree, once I've added the translated strings into them Thanks for any help, regards,
Denis
So, according to that page, I ran svn co svn://anonsvn.kde.org/home/kde/branches/trinity ./ Now I have the latest trinity sources on my computer but still don't know what to do with them, to get the french po files updated. I don't see any Makefile somewhere with which I could run something like "make i18n" or "make po".
Denis
Le 25/10/2010 07:53, Denis Prost a écrit :
Sorry, I missed this one : http://trinity.pearsoncomputing.net/wiki/bin/view/Developers/HowToBuild It seems that there is eveything I need to start here. Regards,
Denis
Le 25/10/2010 07:44, Denis Prost a écrit :
Hi everyone,
Still no answer, nobody can help me ? the only thing I need is updated po files for trinity 3.5.12, so that I can translate the new strings. Regards,
Denis
Le 17/10/2010 15:19, Denis Prost a écrit :
Hi everyone,
no answer, so I'm trying to find my way myself to translation process ! I tried to start with :
svn import /home/denis/Bureau/trinity http://websvn.kde.org/branches/trinity/ -m nomsg --non-interactive
but got an error message :
svn: Repository moved permanently to '/branches/trinity/'; please relocate
I'm really new to svn, can anyone help me to find out what's happening ?
Thanks,
Denis
Le 11/10/2010 17:13, Denis Prost a écrit :
Hi everyone,
this is my first post to the list. I proposed myself to translate new strings into french and Tim advised me to post here my questions. I know how to use kbabel or poedit, but that's about all. I would need someone to tell me what are the steps to follow to :
- get po files updated with new strings corresponding to the
added features since 3.5.10 2) update these po files in the source tree, once I've added the translated strings into them Thanks for any help, regards,
Denis
On Mon, Oct 25, 2010 at 08:12, Denis Prost denis.prost@wanadoo.fr wrote:
So, according to that page, I ran svn co svn://anonsvn.kde.org/home/kde/branches/trinity ./ Now I have the latest trinity sources on my computer but still don't know what to do with them, to get the french po files updated. I don't see any Makefile somewhere with which I could run something like "make i18n" or "make po".
Denis
Please don't top post or send html messages. It drives my Thunderbird crazy by displaying tiny font.
++ You need to edit the po files directly ++ They should be in the po directory. I'm assuming that you can use a special program to do this.
As far as I know, you don't need to run "make po" or something.
Le 25/10/2010 17:55, Robert Xu a écrit :
Please don't top post or send html messages. It drives my Thunderbird crazy by displaying tiny font.
++ You need to edit the po files directly ++ They should be in the po directory. I'm assuming that you can use a special program to do this.
As far as I know, you don't need to run "make po" or something.
Sorry for the mess, Robert, I'll take care in the future ! I know how to edit po files (I'll use poedit, kbabel crashes, bug reported) but I need them to be up to date. For example, the adding of a search field in the K menu involved a new config option in kicker config dialog "Show search field in K menu". I'd like to translate it but there is no such string in any po files of the kde-i18n-fr I got trough svn. I guess these po files should be updated from new trinity source code. Can the trinity developers take care of that ? This is all I need to start french translation ! Thanks,
Denis
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.
Le 25/10/2010 23:00, Robert Xu a écrit :
On Mon, Oct 25, 2010 at 15:37, Denis Prostdenis.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.
Regards,
Denis
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 Prostdenis.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/
Le 26/10/2010 17:51, Robert Xu a écrit :
On Tue, Oct 26, 2010 at 02:32, Denis Prostdenis.prost@wanadoo.fr wrote:
Le 25/10/2010 23:00, Robert Xu a écrit :
On Mon, Oct 25, 2010 at 15:37, Denis Prostdenis.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
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 Prostdenis.prost@wanadoo.fr wrote:
Le 25/10/2010 23:00, Robert Xu a écrit :
On Mon, Oct 25, 2010 at 15:37, Denis Prostdenis.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... 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
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 Prostdenis.prost@wanadoo.fr wrote:
Le 25/10/2010 23:00, Robert Xu a écrit :
On Mon, Oct 25, 2010 at 15:37, Denis Prostdenis.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...
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
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 Prostdenis.prost@wanadoo.fr wrote:
Le 25/10/2010 23:00, Robert Xu a écrit :
On Mon, Oct 25, 2010 at 15:37, Denis Prostdenis.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... 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
On Sat, Oct 30, 2010 at 16:18, 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 Prostdenis.prost@wanadoo.fr wrote:
Le 25/10/2010 23:00, Robert Xu a écrit :
On Mon, Oct 25, 2010 at 15:37, Denis Prostdenis.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... 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,
I recommend asking Timothy Pearson on how to do this. You can see this: http://trinity.pearsoncomputing.net/wiki/bin/view/Developers/HowToBuild and it'll tell you have to run make -f admin/Makefile.common.... Then from there I suppose you could look at Makefile.in and such.
On Sat, Oct 30, 2010 at 16:18, 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 Prostdenis.prost@wanadoo.fr wrote:
Le 25/10/2010 23:00, Robert Xu a écrit : > > On Mon, Oct 25, 2010 at 15:37, Denis Prostdenis.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... 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,
I recommend asking Timothy Pearson on how to do this. You can see this: http://trinity.pearsoncomputing.net/wiki/bin/view/Developers/HowToBuild and it'll tell you have to run make -f admin/Makefile.common.... Then from there I suppose you could look at Makefile.in and such.
-- later, Robert Xu
Sorry, I do not know how to do this either. I never was involved with the translation arm of KDE, so it's just something I never learned to do.
Tim
On Sat, Oct 30, 2010 at 9:47 PM, Timothy Pearson < kb9vqf@pearsoncomputing.net> wrote:
On Sat, Oct 30, 2010 at 16:18, 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 Prostdenis.prost@wanadoo.fr wrote: > > Le 25/10/2010 23:00, Robert Xu a écrit : >> >> On Mon, Oct 25, 2010 at 15:37, Denis Prostdenis.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...
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,
I recommend asking Timothy Pearson on how to do this. You can see this: http://trinity.pearsoncomputing.net/wiki/bin/view/Developers/HowToBuild and it'll tell you have to run make -f admin/Makefile.common.... Then from there I suppose you could look at Makefile.in and such.
-- later, Robert Xu
Sorry, I do not know how to do this either. I never was involved with the translation arm of KDE, so it's just something I never learned to do.
Tim
The obvious first step (after downloading and unpacking the sources, of
course) is to find where the original strings are, then translate those into whatever the target locale. You'd then need to follow whatever the format for the project is in saving the translated strings into their own locale files (generally speaking). I can't be specific to any particular project, it is simply an observation that most projects keep their language files organized in a separate directory inside the sources, so I can't be specific to KDE3.
Le 31/10/2010 03:09, Kristopher Gamrat a écrit :
On Sat, Oct 30, 2010 at 9:47 PM, Timothy Pearson <kb9vqf@pearsoncomputing.net mailto:kb9vqf@pearsoncomputing.net> wrote:
> On Sat, Oct 30, 2010 at 16:18, Denis Prost <denis.prost@wanadoo.fr <mailto: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 <mailto: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 <mailto: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, >> > > I recommend asking Timothy Pearson on how to do this. > You can see this: > http://trinity.pearsoncomputing.net/wiki/bin/view/Developers/HowToBuild > and it'll tell you have to run make -f admin/Makefile.common.... > Then from there I suppose you could look at Makefile.in and such. > > -- > later, Robert Xu > Sorry, I do not know how to do this either. I never was involved with the translation arm of KDE, so it's just something I never learned to do. TimThe obvious first step (after downloading and unpacking the sources, of course) is to find where the original strings are, then translate those into whatever the target locale. You'd then need to follow whatever the format for the project is in saving the translated strings into their own locale files (generally speaking). I can't be specific to any particular project, it is simply an observation that most projects keep their language files organized in a separate directory inside the sources, so I can't be specific to KDE3.
-- Kris "Piki" Ark Linux Webmaster Wannabe Ark Linux packager
Thanks to all of you for your answers. It seems that I have to restart from Tim HowToBuild page. But I'm stuck with /<path to your system's libool.m4 file> and //<path to your system's ltmain.sh file> /What are these files, where can I find them (locate did not find them) ? Thanks,
Regards / /
On Sun, Oct 31, 2010 at 3:11 AM, Denis Prost denis.prost@wanadoo.fr wrote:
Le 31/10/2010 03:09, Kristopher Gamrat a écrit :
On Sat, Oct 30, 2010 at 9:47 PM, Timothy Pearson < kb9vqf@pearsoncomputing.net mailto:kb9vqf@pearsoncomputing.net> wrote:
On Sat, Oct 30, 2010 at 16:18, Denis Prost
<denis.prost@wanadoo.fr mailto: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 mailto: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 mailto: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...
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,
I recommend asking Timothy Pearson on how to do this. You can see this:
http://trinity.pearsoncomputing.net/wiki/bin/view/Developers/HowToBuild
and it'll tell you have to run make -f admin/Makefile.common.... Then from there I suppose you could look at Makefile.in and such.
-- later, Robert Xu
Sorry, I do not know how to do this either. I never was involved with the translation arm of KDE, so it's just something I never learned to do.
Tim
The obvious first step (after downloading and unpacking the sources, of course) is to find where the original strings are, then translate those into whatever the target locale. You'd then need to follow whatever the format for the project is in saving the translated strings into their own locale files (generally speaking). I can't be specific to any particular project, it is simply an observation that most projects keep their language files organized in a separate directory inside the sources, so I can't be specific to KDE3.
-- Kris "Piki" Ark Linux Webmaster Wannabe Ark Linux packager
Thanks to all of you for your answers. It seems that I have to restart from Tim HowToBuild page. But I'm stuck with /<path to your system's libool.m4 file> and //<path to your system's ltmain.sh file> /What are these files, where can I find them (locate did not find them) ? Thanks,
Regards / /
I think (not quite sure) they may be related to Autoconf and Automake. Make
sure you have them installed, then run the updatedb command as root to update the file database for locate. From there, hopefully those files will appear. If not, post back and someone else will come to the aid.
Le 31/10/2010 08:43, Kristopher Gamrat a écrit :
On Sun, Oct 31, 2010 at 3:11 AM, Denis Prost <denis.prost@wanadoo.fr mailto:denis.prost@wanadoo.fr> wrote:
Le 31/10/2010 03:09, Kristopher Gamrat a écrit : On Sat, Oct 30, 2010 at 9:47 PM, Timothy Pearson <kb9vqf@pearsoncomputing.net <mailto:kb9vqf@pearsoncomputing.net> <mailto:kb9vqf@pearsoncomputing.net <mailto:kb9vqf@pearsoncomputing.net>>> wrote: > On Sat, Oct 30, 2010 at 16:18, Denis Prost <denis.prost@wanadoo.fr <mailto:denis.prost@wanadoo.fr> <mailto:denis.prost@wanadoo.fr <mailto: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 <mailto:denis.prost@wanadoo.fr> <mailto:denis.prost@wanadoo.fr <mailto: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 <mailto:denis.prost@wanadoo.fr> <mailto:denis.prost@wanadoo.fr <mailto: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, >> > > I recommend asking Timothy Pearson on how to do this. > You can see this: > http://trinity.pearsoncomputing.net/wiki/bin/view/Developers/HowToBuild > and it'll tell you have to run make -f admin/Makefile.common.... > Then from there I suppose you could look at Makefile.in and such. > > -- > later, Robert Xu > Sorry, I do not know how to do this either. I never was involved with the translation arm of KDE, so it's just something I never learned to do. Tim The obvious first step (after downloading and unpacking the sources, of course) is to find where the original strings are, then translate those into whatever the target locale. You'd then need to follow whatever the format for the project is in saving the translated strings into their own locale files (generally speaking). I can't be specific to any particular project, it is simply an observation that most projects keep their language files organized in a separate directory inside the sources, so I can't be specific to KDE3. -- Kris "Piki" Ark Linux Webmaster Wannabe Ark Linux packager Thanks to all of you for your answers. It seems that I have to restart from Tim HowToBuild page. But I'm stuck with /<path to your system's libool.m4 file> and //<path to your system's ltmain.sh file> /What are these files, where can I find them (locate did not find them) ? Thanks, Regards / /I think (not quite sure) they may be related to Autoconf and Automake. Make sure you have them installed, then run the updatedb command as root to update the file database for locate. From there, hopefully those files will appear. If not, post back and someone else will come to the aid.
Thanks Kris, with automake installed and after updatedb, I can locate these files. Now, I'm going on for the build process hoping that it will provide me Makefiles with "messages" target at the end.
Denis
Le 31/10/2010 09:17, Denis Prost a écrit :
Le 31/10/2010 08:43, Kristopher Gamrat a écrit :
On Sun, Oct 31, 2010 at 3:11 AM, Denis Prost <denis.prost@wanadoo.fr mailto:denis.prost@wanadoo.fr> wrote:
Le 31/10/2010 03:09, Kristopher Gamrat a écrit : On Sat, Oct 30, 2010 at 9:47 PM, Timothy Pearson<kb9vqf@pearsoncomputing.net mailto:kb9vqf@pearsoncomputing.net <mailto:kb9vqf@pearsoncomputing.net mailto:kb9vqf@pearsoncomputing.net>> wrote:
On Sat, Oct 30, 2010 at 16:18, Denis Prost
<denis.prost@wanadoo.fr mailto:denis.prost@wanadoo.fr <mailto:denis.prost@wanadoo.fr mailto: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.frmailto:denis.prost@wanadoo.fr <mailto:denis.prost@wanadoo.fr mailto: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.frmailto:denis.prost@wanadoo.fr <mailto:denis.prost@wanadoo.fr mailto: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
providingall instructions needed would help. (not forgetting that translators are just translators and may
be veryignorant besides !). Regards,
Denis
Maybe what we're looking for is here :
http://developer.kde.org/documentation/library/kdeqt/kde3arch/kde-i18n-howto...
especially chapter 3 about Makefile.am. As far as I understand (I just checked quickly) It seems that
"makemessages" should be run periodically on the source tree by its administrator to update the pot files, followed by some command to merge the
new potfiles with the existing corresponding po files for each language (at
presenttime, 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 mergingand then for the translators to update them.
Regards,
Denis
As long as there is no centralized process to update the po
files, I'mtrying to do it myself, but I don't know enough of the
development toolsto achieve it. Maybe someone might help me : I'd like to run "make messages" in kdebase/kicker source
directory, butthere is no Makefile in it, only Makefile.am. How can I
generateMakefile from it, what command should I run ? Thanks,
I recommend asking Timothy Pearson on how to do this. You can see this:
http://trinity.pearsoncomputing.net/wiki/bin/view/Developers/HowToBuild
and it'll tell you have to run make -f admin/Makefile.common.... Then from there I suppose you could look at Makefile.in and
such.-- later, Robert Xu
Sorry, I do not know how to do this either. I never was involved with the translation arm of KDE, so it's just something I never learned to do. Tim The obvious first step (after downloading and unpacking the sources, of course) is to find where the original strings are, then translate those into whatever the target locale. You'd then need to follow whatever the format for the project is in saving the translated strings into their own locale files (generally speaking). I can't be specific to any particular project, it is simply an observation that most projects keep their language files organized in a separate directory inside the sources, so I can't be specific to KDE3. -- Kris "Piki" Ark Linux Webmaster Wannabe Ark Linux packager Thanks to all of you for your answers. It seems that I have to restart from Tim HowToBuild page. But I'm stuck with /<path to your system's libool.m4 file> and //<path to your system's ltmain.sh file> /What are these files, where can I find them (locate did not find them) ? Thanks, Regards / /I think (not quite sure) they may be related to Autoconf and Automake. Make sure you have them installed, then run the updatedb command as root to update the file database for locate. From there, hopefully those files will appear. If not, post back and someone else will come to the aid.
Thanks Kris, with automake installed and after updatedb, I can locate these files. Now, I'm going on for the build process hoping that it will provide me Makefiles with "messages" target at the end.
Some news : here is where I am in my attempt to achieve the translation process :
1) For every module, I ran : cp -Rp /<path to your system's libtool.m4 file>/ admin/libtool.m4.in cp -Rp /<path to your system's ltmain.sh file>/ admin/ltmain.sh make -f admin/Makefile.common ./configure (with options as indicated by Tim for debian)
2) after the operations, some of the generated Makefiles had a "messages" target in them, to produce the corresponding pot file
For example, in kdebase/kcontrol/kicker/Makefile :
messages: rc.cpp (cd ../../kicker/data/tiles ; ls *_tiny_up.png) | perl -p -e \ 's/(.*)_tiny_up.png/i18n("\u$$1");/; s/[_ ]+(.)/ \u$$1/g' >> rc.cpp $(XGETTEXT) *.cpp -o $(podir)/kcmkicker.pot
3) so I tried "make messages" on one of them :
=> a) first error : "missing separator (did you mean TAB instead of 8 spaces?)." It was solved performing unexpand on the Makefile (don't know why tabs were replaced by spaces in Makefile, is there any way to avoid this ?)
b) second error : "No rule to make target `rc.cpp'" I googled for that error : as far as I understand, it seems that this is the extractrc script that did not do its job extracting the i18n strings to generate rc.cpp. But I don't know where in the build process it is supposed to be called. Should I have run "make" before ? (I'm trying as much as possible to avoid a full build process, that should not be required just for extracting i18n strings from source).
Thanks for any help,
Denis
On Sun, 31 Oct 2010 08:11:50 +0100 Denis Prost wrote:
[snip]
Thanks to all of you for your answers. It seems that I have to restart from Tim HowToBuild page. But I'm stuck with /<path to your system's libool.m4 file> and //<path to your system's ltmain.sh file> /What are these files, where can I find them (locate did not find them) ? Thanks,
libool is a typo - it should read 'libtool' and should be part of your systems gcc/make/autoconf group of files
Could someone please fix this on the wiki?
Cheers
John NZ
On Sun, Oct 31, 2010 at 03:11, Denis Prost denis.prost@wanadoo.fr wrote:
Thanks to all of you for your answers. It seems that I have to restart from Tim HowToBuild page. But I'm stuck with /<path to your system's libool.m4 file> and //<path to your system's ltmain.sh file> /What are these files, where can I find them (locate did not find them) ? Thanks,
Actually, I never found a need for those files to be copied.
On 11/10/2010 17:13, Denis Prost wrote:
Hi everyone,
this is my first post to the list. I proposed myself to translate new strings into french and Tim advised me to post here my questions. I know how to use kbabel or poedit, but that's about all. I would need someone to tell me what are the steps to follow to :
- get po files updated with new strings corresponding to the added
features since 3.5.10 2) update these po files in the source tree, once I've added the translated strings into them Thanks for any help, regards,
Denis
Hi,
What's up with your translation process? I also thought about contributing to translate to french. I'm not a Makefile expert, but maybe I can help (I love to fix things!)
Nicolas.
-
Denis Prost -
John -
Kristopher Gamrat -
Nicolas BERCHER -
Robert Xu -
Timothy Pearson