Thread: French translation
A (renewed) effort has been launched by Guillaume Lelarge (with the help of Jerome Seyler and myself) to translate PostgreSQL to French. The goal is to translate the various applications, the manuals (doc and man pages), as well as the FAQs. Even if we are not starting completely from scratch, since some elements of previous versions had been translated (we are working on 7.4), this is still quite a challenge. As such we are looking for people who would like to participate to help us complete the project faster. We have a web site to inform about and coordinate our work: http://pgsql-fr.tuxfamily.org/. It's not quite ready yet, but it displays a state of the project. It also contains a CVS repository, a glossary of translations of technical terms, etc. We should also soon have a separate mailing list dedicated only to this translation effort. We hope many French speakers will join us on this endeavour, especially for proofreading. Cheers. --------------- Francois Home page: http://www.monpetitcoin.com/ "Would Descartes have programmed in Pascal?" - Umberto Eco
I cannot help you as my French is pretty old, mais, bon chance! Francois Suter wrote: > A (renewed) effort has been launched by Guillaume Lelarge (with the > help of Jerome Seyler and myself) to translate PostgreSQL to French. > > The goal is to translate the various applications, the manuals (doc > and man pages), as well as the FAQs. Even if we are not starting > completely from scratch, since some elements of previous versions had > been translated (we are working on 7.4), this is still quite a challenge. > > As such we are looking for people who would like to participate to > help us complete the project faster. We have a web site to inform > about and coordinate our work: http://pgsql-fr.tuxfamily.org/. It's > not quite ready yet, but it displays a state of the project. It also > contains a CVS repository, a glossary of translations of technical > terms, etc. We should also soon have a separate mailing list dedicated > only to this translation effort. > > We hope many French speakers will join us on this endeavour, > especially for proofreading. > > Cheers. > > --------------- > Francois > > Home page: http://www.monpetitcoin.com/ > > "Would Descartes have programmed in Pascal?" - Umberto Eco > > > ---------------------------(end of broadcast)--------------------------- > TIP 6: Have you searched our list archives? > > http://archives.postgresql.org >
On Mon, Sep 01, 2003 at 06:24:06PM +0200, Francois Suter wrote: > A (renewed) effort has been launched by Guillaume Lelarge (with the > help of Jerome Seyler and myself) to translate PostgreSQL to French. > > The goal is to translate the various applications, the manuals (doc and > man pages), as well as the FAQs. Even if we are not starting completely > from scratch, since some elements of previous versions had been > translated (we are working on 7.4), this is still quite a challenge. How are you planning to translate the SGML documentation? More to the point, how do you plan to keep the translations up to date? I ask because I want to organize people to translate the documentation to spanish. There's already a translated version, but it's for 6.5 (eons old) and they have made little progress in the updating. What I want to avoid is having to check by hand which pages change and where... do you have some infrastructure for this? I've read somewhere that the KDE project uses conversion tool from SGML to PO, and translate using the PO tools (which can detect fuzzy strings, already translated strings and such), but I haven't researched it. -- Alvaro Herrera (<alvherre[a]dcc.uchile.cl>) "Sallah, I said NO camels! That's FIVE camels; can't you count?" (Indiana Jones)
> How are you planning to translate the SGML documentation? More to the > point, how do you plan to keep the translations up to date? Unfortunately we are not *that* well organized. We're using mostly simple text editors for working with both SGML and PO files and haven't yet really given any thought about keeping the translation up to date. Now that starts me thinking. I would say one way to do it would be to keep all original (i.e. in English) files that we used for translation (it's easy enough to flag them in our CVS repository). Then we would from time to time get the latest versions of, say, the manual in SGML format and run a script over all files that invokes something like diff. Just off the top of my head, that would need digging. Then again, maybe someone has done something already. Any input from other translators? Cheers. --------------- Francois Home page: http://www.monpetitcoin.com/ "Would Descartes have programmed in Pascal?" - Umberto Eco
Francois Suter writes: > Now that starts me thinking. I would say one way to do it would be to > keep all original (i.e. in English) files that we used for translation > (it's easy enough to flag them in our CVS repository). Then we would > from time to time get the latest versions of, say, the manual in SGML > format and run a script over all files that invokes something like > diff. Just off the top of my head, that would need digging. That's pretty much it. In your translated files you keep a comment that identifies which CVS revision of the original file the translation is based on. For the diff'ing you can just use the cvsweb. -- Peter Eisentraut peter_e@gmx.net
Francois Suter wrote: > Unfortunately we are not *that* well organized. We're using mostly > simple text editors for working with both SGML and PO files and > haven't yet really given any thought about keeping the translation up > to date. > > Now that starts me thinking. I would say one way to do it would be to > keep all original (i.e. in English) files that we used for translation > (it's easy enough to flag them in our CVS repository). Then we would > from time to time get the latest versions of, say, the manual in SGML > format and run a script over all files that invokes something like > diff. Just off the top of my head, that would need digging. > > Then again, maybe someone has done something already. Any input from > other translators? In the brazilian project we're using only text editors and working on the SGML files. When we updated the docs from version 7.2 to 7.3 we checked the changes manually, but we had only the reference guide translated at that time. I still don't know how we're gonna make it for the 7.3 -> 7.4 update. Does anyone knows some other way? -- Diogo Biazus diogo@ikono.com.br http://www.ikono.com.br
On Thu, Sep 04, 2003 at 02:01:18PM +0200, Diogo Biazus wrote: > Francois Suter wrote: > > >Unfortunately we are not *that* well organized. We're using mostly > >simple text editors for working with both SGML and PO files and > >haven't yet really given any thought about keeping the translation up > >to date. > In the brazilian project we're using only text editors and working on > the SGML files. > When we updated the docs from version 7.2 to 7.3 we checked the changes > manually, but we had only the reference guide translated at that time. I > still don't know how we're gonna make it for the 7.3 -> 7.4 update. > Does anyone knows some other way? Nope. Maybe it's time to start investigating the KDE way. http://i18n.kde.org/translation-howto/doc-translation.html I don't have much time ATM though; will look into this later if no one comes to doing it. Looks like a migration to XML DocBook will be needed... -- Alvaro Herrera (<alvherre[@]dcc.uchile.cl>) "Cuando miro a alguien, mas me atrae como cambia que quien es" (J. Binoche)
Le Mercredi 3 Septembre 2003 03:47, Alvaro Herrera a écrit : > On Mon, Sep 01, 2003 at 06:24:06PM +0200, Francois Suter wrote: > > A (renewed) effort has been launched by Guillaume Lelarge (with the > > help of Jerome Seyler and myself) to translate PostgreSQL to French. > > > > The goal is to translate the various applications, the manuals (doc and > > man pages), as well as the FAQs. Even if we are not starting completely > > from scratch, since some elements of previous versions had been > > translated (we are working on 7.4), this is still quite a challenge. > > How are you planning to translate the SGML documentation? More to the > point, how do you plan to keep the translations up to date? > There's a lot of way to do this. Let's say you're able to have a complete translation for the 7.4 documentation. You put it in your own CVS. When you have some time to update your translation, all you need to do is getting names of modified files from a cvs update of the original postgresql cvs. With the files' name and cvsweb, it will really be easy to know what modifications have been done, and you can update the translation of these files. This is the way I chose for the LFS and BLFS documentation and it work quite simply. Another way is to put the english version and the translated one in your cvs repository. As soon as you finish your translations, you get the new files (if any) by a cvs update, put them in your own cvs. This way, you have a way to know which modification have been done (cvs web, cvs diff, etc.). You can also create po files from sgml and translate the po files. > I ask because I want to organize people to translate the documentation > to spanish. There's already a translated version, but it's for 6.5 > (eons old) and they have made little progress in the updating. What I > want to avoid is having to check by hand which pages change and where... > do you have some infrastructure for this? > We also have some old translations but it will be really hard to use them. > I've read somewhere that the KDE project uses conversion tool from SGML > to PO, and translate using the PO tools (which can detect fuzzy strings, > already translated strings and such), but I haven't researched it. Yes, some tools can save sentences ou para of your sgml files in .po files. It could be an interesting way to do it. As you said, the KDE team uses this method with great success but I didn't experience it myself. -- Guillaume <!-- http://absfr.tuxfamily.org/ http://pgsql-fr.tuxfamily.org/ -->.
Le Mercredi 3 Septembre 2003 19:25, Peter Eisentraut a écrit : > That's pretty much it. In your translated files you keep a comment that > identifies which CVS revision of the original file the translation is > based on. For the diff'ing you can just use the cvsweb. Actually, that's not exactly the way we are doing it. I just keep the original cvs files to be able to update them when we would have done a first "pass". But this starts me thinking that I would be quite embarassed if my hard disk broke :-/ Putting them in a CVS or adding a comment could be a better way. Thanks. -- Guillaume <!-- http://absfr.tuxfamily.org/ http://pgsql-fr.tuxfamily.org/ -->.