Re: Status of manpages-fr -- help needed?
Jean-Philippe MENGUAL Le 06/10/2019 à 14:51, Mario Blättermann a écrit : > Am So., 6. Okt. 2019 um 14:02 Uhr schrieb Jean-Philippe MENGUAL > : >> >> >> Le 06/10/2019 à 13:46, Mario Blättermann a écrit : >>> Hello Jean-Philippe, >>> […] >>> While copying the strings into the script and testing, I found some >>> more translatable parts. Updated po file is attached. >> >> Forgotten it seems :) >> > OK, now with attachment. Here is my translation I hope the tam will have a look on the script generation, with more experience than I > > Best Regards, > Mario > scripts-fr.po.gz Description: application/gzip
Re: Status of manpages-fr -- help needed?
Am So., 6. Okt. 2019 um 14:02 Uhr schrieb Jean-Philippe MENGUAL : > > > Le 06/10/2019 à 13:46, Mario Blättermann a écrit : > > Hello Jean-Philippe, > > […] > > While copying the strings into the script and testing, I found some > > more translatable parts. Updated po file is attached. > > Forgotten it seems :) > OK, now with attachment. Best Regards, Mario # French translation of the manpages-l10n scripts # Copyright © of this file: # This file is distributed under the same license as the manpages-l10n package. # Jean-Philippe Mengual , 2019. # msgid "" msgstr "" "Project-Id-Version: manpages-l10n\n" "POT-Creation-Date: 2019-10-06 13:39+02:00\n" "PO-Revision-Date: 2019-10-06 12:41+0200\n" "Last-Translator: Jean-Philippe Mengual \n" "Language-Team: French \n" "Language: fr\n" "MIME-Version: 1.0\n" "Content-Type: text/plain; charset=UTF-8\n" "Content-Transfer-Encoding: 8bit\n" "X-Generator: Lokalize 1.0\n" "Plural-Forms: nplurals=2; plural=(n > 1);\n" #. TRANSLATORS: %s is the timestamp of the status page. #: public/generate-stats-page.sh:47 msgid "Time: %s" msgstr "" #. TRANSLATORS: Replace »English« with the name of your language. This line #. becomes the first header line in *.po files. #: po/create-new-translation.sh:50 msgid "# English translation of manpages" msgstr "# Traduction en français des pages de manuel" #. TRANSLATORS: Replace »LANGUAGE« with the name of your language and add the #. address of the language team which is responsible for comments, proposals, #. bug reports etc. #: po/create-new-translation.sh:59 msgid "Language-Team: LANGUAGE " msgstr "French " #. TRANSLATORS: Replace »English« with the name of your language. #. %d will be substituted by the translator name and his/her mail address. #: po/generate-addendum.sh:42 msgid "The English translation of this man page has been created by %d." msgstr "La traduction française de cette page de manuel a été créée par %d." #. TRANSLATORS: Replace »English« with the name of your language. #. %d and %s will be substituted by the translator names and his/her mail #. addresses. This will be applied in case of two translators. #: po/generate-addendum.sh:43 msgid "The English translation of this man page has been created by %d and %s." msgstr "" "La traduction française de cette page de manuel a été créée par %d et %s." #. TRANSLATORS: Replace »English« with the name of your language. #. %d and %s will be substituted by the translator names and his/her mail #. addresses. This will be applied in case of three or more translators. #: po/generate-addendum.sh:43 msgid "" "The English translation of this man page has been created by %d, %s and %z." msgstr "" "La traduction française de cette page de manuel a été créée par %d, %s et %z." #. TRANSLATORS: %s is the timestamp of the status page. #: public/generate-stats-page.sh:95 msgid "Overview" msgstr "" #: public/generate-stats-page.sh:98 msgid "View Git Repository" msgstr "" #: public/generate-stats-page.sh:151 msgid "Name" msgstr "" #: public/generate-stats-page.sh:152 msgid "Percentage" msgstr "" #: public/generate-stats-page.sh:153 msgid "Translations until 80%" msgstr "" #: public/generate-stats-page.sh:154 msgid "Statistics" msgstr "" #. TRANSLATORS: This is the section title for an addendum, which will be added #. to each translated man page. #: license.add:1 msgid "TRANSLATION" msgstr "TRADUCTION" #. TRANSLATORS: This disclaimer is the license declaration, added to each #. translated man page. Make sure you use the correct mail address of the team #. which is responsible for bug reports. #: license.add:2 msgid "" "This translation is free documentation; please refer to the GNU General " "Public License version 3 or later regarding the conditions for copying and " "distribution. There is no LEGAL RESPONSIBILITY.\n" "\n" "If you find a bug in the translation of this manual page, please write to " "." msgstr "" "Cette traduction est une documentation libre ; veuillez vous reporter à la " "GNU General Public License version 3 concernant les conditions de copie et " "de distribution. Il n'y a aucune RESPONSABILITÉ LÉGALE.\n" "\n" "Si vous découvrez un bogue dans la traduction de cette page de manuel, " "veuillez envoyer un message à ." #. TRANSLATORS: Replace »English« with the name of your language. #. This is the header line of the status pages. #: public/generate-stats-page.sh:42 msgid "English translation of man pages" msgstr "Traduction française des pages de manuel" #: public/generate-stats-page.sh:46 msgid "List of incompletely translated files" msgstr "Liste des fichiers dont la traduction n'est pas complète" #: public/generate-stats-page.sh:65 msgid "List of untranslated files" msgstr "Liste des fichiers non traduits" #. TRANSLATORS: %s expands to a number. #: public/generate-stats-page.sh:114 msgid "%s untranslated messages." msgstr "%s messages non traduits." #. TRANSLATORS: %s expands to a number. #: public/generate-stats-page.sh:164 #, fuzzy msgid "%s file is
Re: Status of manpages-fr -- help needed?
Le 06/10/2019 à 13:46, Mario Blättermann a écrit : > Hello Jean-Philippe, > > Am So., 6. Okt. 2019 um 13:35 Uhr schrieb Jean-Philippe MENGUAL > : >> >> Hi, >> >> Thanks Jean-Pierre for the review. Mario, here is the definitive version >> of the translation. >> > While copying the strings into the script and testing, I found some > more translatable parts. Updated po file is attached. Forgotten it seems :) Best regards > > After checking out our Git repo, you can test the creation of the > status pages by running the script public/generate-stats-page-fr.sh. > Please have a look at this and tell me about any mistakes or > peculiarities. > > There is a mistake in one of the translated strings: > > #. TRANSLATORS: %s expands to a number. > #: public/generate-stats-page.sh:164 > msgid "%s file is incompletely translated" > msgid_plural "%s files are incompletely translated" > msgstr[0] "%s fichiers ne sont pas complètement traduits" > msgstr[1] "%s fichier n'est pas complètement traduit" > > Singular and plural forms are swapped. > > Best Regards, > Mario >
Re: Status of manpages-fr -- help needed?
Hello Jean-Philippe, Am So., 6. Okt. 2019 um 13:35 Uhr schrieb Jean-Philippe MENGUAL : > > Hi, > > Thanks Jean-Pierre for the review. Mario, here is the definitive version > of the translation. > While copying the strings into the script and testing, I found some more translatable parts. Updated po file is attached. After checking out our Git repo, you can test the creation of the status pages by running the script public/generate-stats-page-fr.sh. Please have a look at this and tell me about any mistakes or peculiarities. There is a mistake in one of the translated strings: #. TRANSLATORS: %s expands to a number. #: public/generate-stats-page.sh:164 msgid "%s file is incompletely translated" msgid_plural "%s files are incompletely translated" msgstr[0] "%s fichiers ne sont pas complètement traduits" msgstr[1] "%s fichier n'est pas complètement traduit" Singular and plural forms are swapped. Best Regards, Mario
Re: Status of manpages-fr -- help needed?
Hi, Thanks Jean-Pierre for the review. Mario, here is the definitive version of the translation. Regards Jean-Philippe MENGUAL Le 06/10/2019 à 13:07, Jean-Philippe MENGUAL a écrit : > > Le 06/10/2019 à 12:51, Mario Blättermann a écrit : >> Hello Jean-Philippe, >> >>> […] >>> I attach a gzip file to avoid the charset problems >>> >>> Regards >> >> One of the translations is incomplete: >> >> #. TRANSLATORS: This disclaimer is the license declaration, added to each >> #. translated man page. Make sure you use the correct mail address of the >> team >> #. which is responsible for bug reports. >> #: license.add:2 >> msgid "" >> "This translation is free documentation; please refer to the GNU General " >> "Public License version 3 or later regarding the conditions for copying and " >> "distribution. There is no LEGAL RESPONSIBILITY.\n" >> "\n" >> "If you find a bug in the translation of this manual page, please write to " >> "." >> msgstr "" >> "Cette traduction est une documentation libre ; veuillez vous reporter à la " >> "GNU General Public License version 3 concernant les conditions de copie et " >> "de distribution. Il n'y a aucune RESPONSABILITÉ LÉGALE." >> >> I'm missing the last sentence (If you find a bug…) > > oops my damn! Sorry. Fixed > > Regards > >> >> Best Regards, >> Mario >> scripts-fr.po.gz Description: application/gzip
Re: Status of manpages-fr -- help needed?
Bonjour, envoi du fichier complet. Amicalement, jipege Le 06/10/2019 à 13:10, Jean-Pierre Giraud a écrit : > Bonjour, > > Le 06/10/2019 à 12:51, Mario Blättermann a écrit : >> Hello Jean-Philippe, >> >>> […] >>> I attach a gzip file to avoid the charset problems >>> >>> Regards >> One of the translations is incomplete: >> >> #. TRANSLATORS: This disclaimer is the license declaration, added to each >> #. translated man page. Make sure you use the correct mail address of the >> team >> #. which is responsible for bug reports. >> #: license.add:2 >> msgid "" >> "This translation is free documentation; please refer to the GNU General " >> "Public License version 3 or later regarding the conditions for copying and " >> "distribution. There is no LEGAL RESPONSIBILITY.\n" >> "\n" >> "If you find a bug in the translation of this manual page, please write to " >> "." >> msgstr "" >> "Cette traduction est une documentation libre ; veuillez vous reporter à la " >> "GNU General Public License version 3 concernant les conditions de copie et " >> "de distribution. Il n'y a aucune RESPONSABILITÉ LÉGALE." >> >> I'm missing the last sentence (If you find a bug…) >> >> Best Regards, >> Mario > Voici une version avec la traduction de la dernière phrase et quelques > suggestions. Je propose de remplacé manpage par page de manuel, > traduction qui est couramment employée sur d.o. > > Amicalement, > > jipege > # French translation of the manpages-l10n scripts # Copyright © of this file: # This file is distributed under the same license as the manpages-l10n package. # Jean-Philippe Mengual , 2019. # msgid "" msgstr "" "Project-Id-Version: manpages-l10n\n" "POT-Creation-Date: 2019-10-03 11:56+02:00\n" "PO-Revision-Date: 2019-10-06 12:41+0200\n" "Last-Translator: Jean-Philippe Mengual \n" "Language-Team: French \n" "Language: fr\n" "MIME-Version: 1.0\n" "Content-Type: text/plain; charset=UTF-8\n" "Content-Transfer-Encoding: 8bit\n" "X-Generator: Lokalize 1.0\n" "Plural-Forms: nplurals=2; plural=(n > 1);\n" #. TRANSLATORS: Replace »English« with the name of your language. This line #. becomes the first header line in *.po files. #: po/create-new-translation.sh:50 msgid "# English translation of manpages" msgstr "# Traduction en français des pages de manuel" #. TRANSLATORS: Replace »LANGUAGE« with the name of your language and add the #. address of the language team which is responsible for comments, proposals, #. bug reports etc. #: po/create-new-translation.sh:59 msgid "Language-Team: LANGUAGE " msgstr "French " #. TRANSLATORS: Replace »English« with the name of your language. #. %d will be substituted by the translator name and his/her mail address. #: po/generate-addendum.sh:42 msgid "The English translation of this man page has been created by %d." msgstr "La traduction française de cette page de manuel a été créée par %d." #. TRANSLATORS: Replace »English« with the name of your language. #. %d and %s will be substituted by the translator names and his/her mail #. addresses. This will be applied in case of two translators. #: po/generate-addendum.sh:43 msgid "The English translation of this man page has been created by %d and %s." msgstr "" "La traduction française de cette page de manuel a été créée par %d et %s." #. TRANSLATORS: Replace »English« with the name of your language. #. %d and %s will be substituted by the translator names and his/her mail #. addresses. This will be applied in case of three or more translators. #: po/generate-addendum.sh:43 msgid "" "The English translation of this man page has been created by %d, %s and %z." msgstr "" "La traduction française de cette page de manuel a été créée par %d, %s et %z." #. TRANSLATORS: This is the section title for an addendum, which will be added #. to each translated man page. #: license.add:1 msgid "TRANSLATION" msgstr "TRADUCTION" #. TRANSLATORS: This disclaimer is the license declaration, added to each #. translated man page. Make sure you use the correct mail address of the team #. which is responsible for bug reports. #: license.add:2 msgid "" "This translation is free documentation; please refer to the GNU General " "Public License version 3 or later regarding the conditions for copying and " "distribution. There is no LEGAL RESPONSIBILITY.\n" "\n" "If you find a bug in the translation of this manual page, please write to " "." msgstr "" "Cette traduction est une documentation libre ; veuillez vous reporter à la " "GNU General Public License version 3 concernant les conditions de copie et " "de distribution. Il n'y a aucune RESPONSABILITà LÃGALE.\n" "\n" "Si vous découvrez un bogue dans la traduction de cette page de manuel, " "veuillez envoyer un message à ." #. TRANSLATORS: Replace »English« with the name of your language. #. This is the header line of the status pages. #: public/generate-stats-page.sh:42 msgid "English translation of man pages" msgstr "Traduction française des pages de manuel" #:
Re: Status of manpages-fr -- help needed?
Bonjour, Le 06/10/2019 à 12:51, Mario Blättermann a écrit : > Hello Jean-Philippe, > >> […] >> I attach a gzip file to avoid the charset problems >> >> Regards > One of the translations is incomplete: > > #. TRANSLATORS: This disclaimer is the license declaration, added to each > #. translated man page. Make sure you use the correct mail address of the team > #. which is responsible for bug reports. > #: license.add:2 > msgid "" > "This translation is free documentation; please refer to the GNU General " > "Public License version 3 or later regarding the conditions for copying and " > "distribution. There is no LEGAL RESPONSIBILITY.\n" > "\n" > "If you find a bug in the translation of this manual page, please write to " > "." > msgstr "" > "Cette traduction est une documentation libre ; veuillez vous reporter à la " > "GNU General Public License version 3 concernant les conditions de copie et " > "de distribution. Il n'y a aucune RESPONSABILITÉ LÉGALE." > > I'm missing the last sentence (If you find a bug…) > > Best Regards, > Mario Voici une version avec la traduction de la dernière phrase et quelques suggestions. Je propose de remplacé manpage par page de manuel, traduction qui est couramment employée sur d.o. Amicalement, jipege --- /home/jpg1/Documents/traductions/l10n/r_s/scripts-fr/scripts-fr.po 2019-10-06 12:55:33.765354961 +0200 +++ /home/jpg1/Documents/traductions/l10n/r_s/scripts-fr/scripts-fr_jpg.po 2019-10-06 13:03:36.307486236 +0200 @@ -21,7 +21,7 @@ #. becomes the first header line in *.po files. #: po/create-new-translation.sh:50 msgid "# English translation of manpages" -msgstr "# Traduction en français des pages de man" +msgstr "# Traduction en français des pages de manuel" #. TRANSLATORS: Replace »LANGUAGE« with the name of your language and add the #. address of the language team which is responsible for comments, proposals, @@ -34,14 +34,15 @@ #. %d will be substituted by the translator name and his/her mail address. #: po/generate-addendum.sh:42 msgid "The English translation of this man page has been created by %d." -msgstr "La traduction française de cette page de man a été créée par %d." +msgstr "La traduction française de cette page de manuel a été créée par %d." #. TRANSLATORS: Replace »English« with the name of your language. #. %d and %s will be substituted by the translator names and his/her mail #. addresses. This will be applied in case of two translators. #: po/generate-addendum.sh:43 msgid "The English translation of this man page has been created by %d and %s." -msgstr "La traduction française de cette page de man a été créée par %d et %s." +msgstr "" +"La traduction française de cette page de manuel a été créée par %d et %s." #. TRANSLATORS: Replace »English« with the name of your language. #. %d and %s will be substituted by the translator names and his/her mail @@ -50,7 +51,7 @@ msgid "" "The English translation of this man page has been created by %d, %s and %z." msgstr "" -"La traduction française de cette page de man a été créée par %d, %s et %z." +"La traduction française de cette page de manuel a été créée par %d, %s et %z." #. TRANSLATORS: This is the section title for an addendum, which will be added #. to each translated man page. @@ -71,14 +72,17 @@ "." msgstr "" "Cette traduction est une documentation libre ; veuillez vous reporter à la " -"GNU General Public License version 3 concernant les conditions de copie et " -"de distribution. Il n'y a aucune RESPONSABILITà LÃGALE." +"GNU General Public License version 3 concernant les conditions de copie et " +"de distribution. Il n'y a aucune RESPONSABILITà LÃGALE.\n" +"\n" +"Si vous découvrez un bogue dans la traduction de cette page de manuel, " +"veuillez envoyer un message à ." #. TRANSLATORS: Replace »English« with the name of your language. #. This is the header line of the status pages. #: public/generate-stats-page.sh:42 msgid "English translation of man pages" -msgstr "Traduction française des pages de man" +msgstr "Traduction française des pages de manuel" #: public/generate-stats-page.sh:46 msgid "List of incompletely translated files" @@ -103,4 +107,4 @@ #. TRANSLATORS: %s expands to a number. #: public/generate-stats-page.sh:210 msgid "In total, %s files are incompletely translated" -msgstr "Au total, %s ne sont pas complètement traduits" +msgstr "Au total, %s fichiers ne sont pas complètement traduits"
Re: Status of manpages-fr -- help needed?
Le 06/10/2019 à 12:51, Mario Blättermann a écrit : > Hello Jean-Philippe, > >> […] >> I attach a gzip file to avoid the charset problems >> >> Regards > > One of the translations is incomplete: > > #. TRANSLATORS: This disclaimer is the license declaration, added to each > #. translated man page. Make sure you use the correct mail address of the team > #. which is responsible for bug reports. > #: license.add:2 > msgid "" > "This translation is free documentation; please refer to the GNU General " > "Public License version 3 or later regarding the conditions for copying and " > "distribution. There is no LEGAL RESPONSIBILITY.\n" > "\n" > "If you find a bug in the translation of this manual page, please write to " > "." > msgstr "" > "Cette traduction est une documentation libre ; veuillez vous reporter à la " > "GNU General Public License version 3 concernant les conditions de copie et " > "de distribution. Il n'y a aucune RESPONSABILITÉ LÉGALE." > > I'm missing the last sentence (If you find a bug…) oops my damn! Sorry. Fixed Regards > > Best Regards, > Mario > scripts-fr.po.gz Description: application/gzip
Re: Status of manpages-fr -- help needed?
Hello Jean-Philippe, > […] > I attach a gzip file to avoid the charset problems > > Regards One of the translations is incomplete: #. TRANSLATORS: This disclaimer is the license declaration, added to each #. translated man page. Make sure you use the correct mail address of the team #. which is responsible for bug reports. #: license.add:2 msgid "" "This translation is free documentation; please refer to the GNU General " "Public License version 3 or later regarding the conditions for copying and " "distribution. There is no LEGAL RESPONSIBILITY.\n" "\n" "If you find a bug in the translation of this manual page, please write to " "." msgstr "" "Cette traduction est une documentation libre ; veuillez vous reporter à la " "GNU General Public License version 3 concernant les conditions de copie et " "de distribution. Il n'y a aucune RESPONSABILITÉ LÉGALE." I'm missing the last sentence (If you find a bug…) Best Regards, Mario
Re: Status of manpages-fr -- help needed?
>>> >>> Thanks for the quick response! Please translate the attached >>> scripts.pot first. It is needed to generate a proper addendum and >>> status pages. Currently, the French status pages are not yet available >> >> hmmm I am not an expert of the tools, but should I translate the .pot >> directly? Usually I translate po files, then the pot generation is done >> via gettext (makefile or whatever). Is it a particular case where I >> should translate the pot directly, or some additional steps to translate >> a po file then regenerate the pot? >> > Don't bother with that. I've generated the *.pot file manually, it is > not based a Gettext workflow. But I think it is the easiest way to get > the translated parts of the scripts, because translators are familiar > with such files. Find a stub French *.po file in the attachment. Great, many thanks >> >>> online. Run the script public/generate-stats-page-fr.sh to get the >>> HTML files locally (in »public«) and view them in your favorite >>> browser. >>> >>> The translation workflow is as follows: Pick a .po file, write an >>> [ITT] mail to the list, then update the translation, send it with >>> [RFR], and once the review is done, send a [DONE] and attach the >>> reviewed po file. I'm subscribed to this list, and when encountering >>> such a [DONE] mail, I will commit this file and add their contents to >>> the compendium. Ideally, the subject line of the mail should follow >>> this scheme: >>> >>> […] man://manpages-l10n/fr/manpage.1.po >>> >>> This makes sure that it can be parsed properly by the robot and it is >>> easier to filter out [DONE] mails which are not relevant for me. >>> Regarding write access to the Git repo, it is up to Tobias as the >>> owner of the repo to grant access. >> >> Should I follow this workflow for the script? I understand that no, I >> should send it to you, but I prefer to ask confirmation > > No, not for this script, but later any *.po file submission for man > pages should follow this workflow. ok. Please find my proposal. I dont think any review is mandatory but if some French members of team want to do it, many thanks. It is a very short translation (12 strings). I attach a gzip file to avoid the charset problems Regards > > Best Regards, > Mario > scripts-fr.po.gz Description: application/gzip
Re: Status of manpages-fr -- help needed?
Hello Jean-Philippe, Am So., 6. Okt. 2019 um 11:36 Uhr schrieb Jean-Philippe MENGUAL : > > >>> > >>> Now we have 1385 po files, but 560 of them cannot be built to > >>> translated man pages because they don't reach the 80% threshold of > >>> Po4a. I've done all I could do, now it is up to real French > >>> translators to update the po files accordingly. > >> > >> Thanks, that is great! I requested to join manpages-l10n-team in case I > >> can help > > > > Thanks for the quick response! Please translate the attached > > scripts.pot first. It is needed to generate a proper addendum and > > status pages. Currently, the French status pages are not yet available > > hmmm I am not an expert of the tools, but should I translate the .pot > directly? Usually I translate po files, then the pot generation is done > via gettext (makefile or whatever). Is it a particular case where I > should translate the pot directly, or some additional steps to translate > a po file then regenerate the pot? > Don't bother with that. I've generated the *.pot file manually, it is not based a Gettext workflow. But I think it is the easiest way to get the translated parts of the scripts, because translators are familiar with such files. Find a stub French *.po file in the attachment. > > > online. Run the script public/generate-stats-page-fr.sh to get the > > HTML files locally (in »public«) and view them in your favorite > > browser. > > > > The translation workflow is as follows: Pick a .po file, write an > > [ITT] mail to the list, then update the translation, send it with > > [RFR], and once the review is done, send a [DONE] and attach the > > reviewed po file. I'm subscribed to this list, and when encountering > > such a [DONE] mail, I will commit this file and add their contents to > > the compendium. Ideally, the subject line of the mail should follow > > this scheme: > > > > […] man://manpages-l10n/fr/manpage.1.po > > > > This makes sure that it can be parsed properly by the robot and it is > > easier to filter out [DONE] mails which are not relevant for me. > > Regarding write access to the Git repo, it is up to Tobias as the > > owner of the repo to grant access. > > Should I follow this workflow for the script? I understand that no, I > should send it to you, but I prefer to ask confirmation No, not for this script, but later any *.po file submission for man pages should follow this workflow. Best Regards, Mario # French translation of the manpages-l10n scripts # Copyright © of this file: # This file is distributed under the same license as the manpages-l10n package. # Jean-Philippe Mengual , 2019. # msgid "" msgstr "" "Project-Id-Version: manpages-l10n\n" "POT-Creation-Date: 2019-10-03 11:56+02:00\n" "PO-Revision-Date: 2019-10-06 11:55+0200\n" "Last-Translator: Jean-Philippe Mengual \n" "Language-Team: French \n" "Language: fr\n" "MIME-Version: 1.0\n" "Content-Type: text/plain; charset=UTF-8\n" "Content-Transfer-Encoding: 8bit\n" "X-Generator: Lokalize 1.0\n" "Plural-Forms: nplurals=2; plural=(n > 1);\n" #. TRANSLATORS: Replace »English« with the name of your language. This line #. becomes the first header line in *.po files. #: po/create-new-translation.sh:50 msgid "# English translation of manpages" msgstr "" #. TRANSLATORS: Replace »LANGUAGE« with the name of your language and add the #. address of the language team which is responsible for comments, proposals, #. bug reports etc. #: po/create-new-translation.sh:59 msgid "Language-Team: LANGUAGE " msgstr "" #. TRANSLATORS: Replace »English« with the name of your language. #. %d will be substituted by the translator name and his/her mail address. #: po/generate-addendum.sh:42 msgid "The English translation of this man page has been created by %d." msgstr "" #. TRANSLATORS: Replace »English« with the name of your language. #. %d and %s will be substituted by the translator names and his/her mail #. addresses. This will be applied in case of two translators. #: po/generate-addendum.sh:43 msgid "The English translation of this man page has been created by %d and %s." msgstr "" #. TRANSLATORS: Replace »English« with the name of your language. #. %d and %s will be substituted by the translator names and his/her mail #. addresses. This will be applied in case of three or more translators. #: po/generate-addendum.sh:43 msgid "" "The English translation of this man page has been created by %d, %s and %z." msgstr "" #. TRANSLATORS: This is the section title for an addendum, which will be added #. to each translated man page. #: license.add:1 msgid "TRANSLATION" msgstr "" #. TRANSLATORS: This disclaimer is the license declaration, added to each #. translated man page. Make sure you use the correct mail address of the team #. which is responsible for bug reports. #: license.add:2 msgid "" "This translation is free documentation; please refer to the GNU General " "Public License version 3 or later regarding the conditions for copying and " "distribution. There is no LEGAL
Re: Status of manpages-fr -- help needed?
>>> >>> Now we have 1385 po files, but 560 of them cannot be built to >>> translated man pages because they don't reach the 80% threshold of >>> Po4a. I've done all I could do, now it is up to real French >>> translators to update the po files accordingly. >> >> Thanks, that is great! I requested to join manpages-l10n-team in case I >> can help > > Thanks for the quick response! Please translate the attached > scripts.pot first. It is needed to generate a proper addendum and > status pages. Currently, the French status pages are not yet available hmmm I am not an expert of the tools, but should I translate the .pot directly? Usually I translate po files, then the pot generation is done via gettext (makefile or whatever). Is it a particular case where I should translate the pot directly, or some additional steps to translate a po file then regenerate the pot? > online. Run the script public/generate-stats-page-fr.sh to get the > HTML files locally (in »public«) and view them in your favorite > browser. > > The translation workflow is as follows: Pick a .po file, write an > [ITT] mail to the list, then update the translation, send it with > [RFR], and once the review is done, send a [DONE] and attach the > reviewed po file. I'm subscribed to this list, and when encountering > such a [DONE] mail, I will commit this file and add their contents to > the compendium. Ideally, the subject line of the mail should follow > this scheme: > > […] man://manpages-l10n/fr/manpage.1.po > > This makes sure that it can be parsed properly by the robot and it is > easier to filter out [DONE] mails which are not relevant for me. > Regarding write access to the Git repo, it is up to Tobias as the > owner of the repo to grant access. Should I follow this workflow for the script? I understand that no, I should send it to you, but I prefer to ask confirmation regards > Best Regards, > Mario >
Re: Status of manpages-fr -- help needed?
Hello Jean-Philippe, Am Sa., 5. Okt. 2019 um 23:42 Uhr schrieb Jean-Philippe MENGUAL : > > > > > Now the import of the French man pages has been finished and a new > > project has been created: > > > > https://salsa.debian.org/manpages-l10n-team/manpages-l10n > > > > The French po files are in po/fr/. The original files from manpages-fr > > and mapages-fr-extra have been merged into one pool. After the import, > > I've created the compendium files in po/fr/common/, filled them with > > translations (as far it was possible for a non-French speaker) and > > synchronized the compendium with the po files. > > > > Now we have 1385 po files, but 560 of them cannot be built to > > translated man pages because they don't reach the 80% threshold of > > Po4a. I've done all I could do, now it is up to real French > > translators to update the po files accordingly. > > Thanks, that is great! I requested to join manpages-l10n-team in case I > can help Thanks for the quick response! Please translate the attached scripts.pot first. It is needed to generate a proper addendum and status pages. Currently, the French status pages are not yet available online. Run the script public/generate-stats-page-fr.sh to get the HTML files locally (in »public«) and view them in your favorite browser. The translation workflow is as follows: Pick a .po file, write an [ITT] mail to the list, then update the translation, send it with [RFR], and once the review is done, send a [DONE] and attach the reviewed po file. I'm subscribed to this list, and when encountering such a [DONE] mail, I will commit this file and add their contents to the compendium. Ideally, the subject line of the mail should follow this scheme: […] man://manpages-l10n/fr/manpage.1.po This makes sure that it can be parsed properly by the robot and it is easier to filter out [DONE] mails which are not relevant for me. Regarding write access to the Git repo, it is up to Tobias as the owner of the repo to grant access. Best Regards, Mario scripts.pot Description: MS-Powerpoint presentation
Re: Status of manpages-fr -- help needed?
> Now the import of the French man pages has been finished and a new > project has been created: > > https://salsa.debian.org/manpages-l10n-team/manpages-l10n > > The French po files are in po/fr/. The original files from manpages-fr > and mapages-fr-extra have been merged into one pool. After the import, > I've created the compendium files in po/fr/common/, filled them with > translations (as far it was possible for a non-French speaker) and > synchronized the compendium with the po files. > > Now we have 1385 po files, but 560 of them cannot be built to > translated man pages because they don't reach the 80% threshold of > Po4a. I've done all I could do, now it is up to real French > translators to update the po files accordingly. Thanks, that is great! I requested to join manpages-l10n-team in case I can help
Re: Status of manpages-fr -- help needed?
Hello all, Am So., 22. Sept. 2019 um 16:23 Uhr schrieb Mario Blättermann : > > Hello all, > > Am So., 8. Sept. 2019 um 11:16 Uhr schrieb Baptiste Jammet > : > > > Hello Helge, et al. > > > First of all thanks for your offer, and sorry for my late (and maybe too > > long) answer. > > > I don't have any "let's do this" solution but I can quickly explain how > > french translation was > > handled. > > > The perkamon/man-pages project [1] is used to handle the infrastructure, > > sharable with > > any language. Next, the perkamon/man-pages-fr [2] is used to translate the > > manpages, > > distro-agnostic. > > > Finally comes Debian packaging, using perkamon as upstream. > > > [1] https://gitlab.com/perkamon/man-pages > > [2] https://gitlab.com/perkamon/man-pages-fr > > The first steps towards up-to-date French manpages are done. I've > imported all the existing > translations (almost all, see below) from the Perkamon repo and > manpages-fr-extra from the latest Debian source package. See [1]. > > I've split the merged po files into single ones, one po file per > source file. Well, this disables synergy effects introduced by keeping > multiple source files together, but we maintain »common« files [2] > which contain a compendium of all gettext messages which occur more > than once in all po files. This way we can edit the compendium files > after any change in the upstream packages and merge the changes back > to the po files. > > Currently the imported po files are in three directories: > > In »fr« we have the po files which have been imported from the Perkamon repo. > > In »fr-extra« we have the po files which have been imported from the > already mentioned latest Debian source package. It would be nice if > you are OK with merging both directories into one. It would be easier > to maintain. > > In »fr-openssl« are some po files from manpages-fr-extra, which are > based on pod sources instead of Groff or Mdoc. This leads to almost > empty po files after importing. I'm in doubt if it makes sense at all > to do the import. The same applies to some of the Lilo manpages, which > are already in fr-extra. > > In general, I would welcome a new project named »manpages-i18n« as the > successor of manpages-de and manpages-fr. Regarding distribution > packaging, it would work like the GUI translations in KDE, which are > all come from a single tarball. This means in particular, we release a > tarball manpages-i18n-x.x.x. and distribution packagers split it into > the langauge-specific parts (manpages-i18n-de, manpages-i18n-fr and so > on for eventually more languages in the future). Moreover, where > applicable, the language packages can be split into »base« and »dev« > packages. By renaming to manpages-i18n, future distribution packages > needs to be declared as updates of the current manpages-de and > manpages-fr/manpages-fr-extra. > > Don't expect too much for the time being. Besides the import itself > I've only added some scripts for handling the updates, and maybe some > pot files are still missing. But the »common« translations are already > present, so if anyone is willing to contribute, please have a look at > the common files first [2]. > > (Please keep Tobias and Helge in CC) > > [1] https://salsa.debian.org/manpages-de-team/manpages-de/tree/import_fr/po/fr > [2] > https://salsa.debian.org/manpages-de-team/manpages-de/tree/import_fr/po/fr/common > Now the import of the French man pages has been finished and a new project has been created: https://salsa.debian.org/manpages-l10n-team/manpages-l10n The French po files are in po/fr/. The original files from manpages-fr and mapages-fr-extra have been merged into one pool. After the import, I've created the compendium files in po/fr/common/, filled them with translations (as far it was possible for a non-French speaker) and synchronized the compendium with the po files. Now we have 1385 po files, but 560 of them cannot be built to translated man pages because they don't reach the 80% threshold of Po4a. I've done all I could do, now it is up to real French translators to update the po files accordingly. The infrastructure inside po/fr/ already works; after checking out the Git repo you can use the scripts for interaction with the compendium, reformatting the po files and so on. The script public/generate-stats-page-fr.sh generates HTML files with a status table for all supported distribution. Sorry, currently it is still German, but it should be self-explaining. When editing po files, please keep the file headers intact. The current structure above the translatro names is needed for a proper addendum for the Groff-Mdoc files. Moreover, I need some additional help with creating the addendum for the Groff/Mdoc files. Please see the attached file scripts.pot and translate it to French. Currently it still doesn't contain all the things we need for the scripts; it will be extended in the near future. The Autotools stack for the package installation doesn't
Re: Status of manpages-fr -- help needed?
Hello all, Am So., 8. Sept. 2019 um 11:16 Uhr schrieb Baptiste Jammet : > Hello Helge, et al. > First of all thanks for your offer, and sorry for my late (and maybe too > long) answer. > I don't have any "let's do this" solution but I can quickly explain how > french translation was > handled. > The perkamon/man-pages project [1] is used to handle the infrastructure, > sharable with > any language. Next, the perkamon/man-pages-fr [2] is used to translate the > manpages, > distro-agnostic. > Finally comes Debian packaging, using perkamon as upstream. > [1] https://gitlab.com/perkamon/man-pages > [2] https://gitlab.com/perkamon/man-pages-fr The first steps towards up-to-date French manpages are done. I've imported all the existing translations (almost all, see below) from the Perkamon repo and manpages-fr-extra from the latest Debian source package. See [1]. I've split the merged po files into single ones, one po file per source file. Well, this disables synergy effects introduced by keeping multiple source files together, but we maintain »common« files [2] which contain a compendium of all gettext messages which occur more than once in all po files. This way we can edit the compendium files after any change in the upstream packages and merge the changes back to the po files. Currently the imported po files are in three directories: In »fr« we have the po files which have been imported from the Perkamon repo. In »fr-extra« we have the po files which have been imported from the already mentioned latest Debian source package. It would be nice if you are OK with merging both directories into one. It would be easier to maintain. In »fr-openssl« are some po files from manpages-fr-extra, which are based on pod sources instead of Groff or Mdoc. This leads to almost empty po files after importing. I'm in doubt if it makes sense at all to do the import. The same applies to some of the Lilo manpages, which are already in fr-extra. In general, I would welcome a new project named »manpages-i18n« as the successor of manpages-de and manpages-fr. Regarding distribution packaging, it would work like the GUI translations in KDE, which are all come from a single tarball. This means in particular, we release a tarball manpages-i18n-x.x.x. and distribution packagers split it into the langauge-specific parts (manpages-i18n-de, manpages-i18n-fr and so on for eventually more languages in the future). Moreover, where applicable, the language packages can be split into »base« and »dev« packages. By renaming to manpages-i18n, future distribution packages needs to be declared as updates of the current manpages-de and manpages-fr/manpages-fr-extra. Don't expect too much for the time being. Besides the import itself I've only added some scripts for handling the updates, and maybe some pot files are still missing. But the »common« translations are already present, so if anyone is willing to contribute, please have a look at the common files first [2]. (Please keep Tobias and Helge in CC) [1] https://salsa.debian.org/manpages-de-team/manpages-de/tree/import_fr/po/fr [2] https://salsa.debian.org/manpages-de-team/manpages-de/tree/import_fr/po/fr/common Best Regards, Mario
Re: Status of manpages-fr -- help needed?
Hello Tobias, > our offer still stands, we're happy to include the French translation in > manpages-de. We should probably find a new name then. :-) Yep. once it works for both languages, we may consider opening it to other teams too, maybe. What about manpages-l10n? > However, I think that this will need some tweaks to our build system, so > please allow me some time to adjust things. Or do you already have a MR ready? No worry, we'll wait for you to be ready of course. I don't have no MR ready, and I did not even start actually working on one. > Regarding the workflow, I'd suggest that every French translator gets write > access to the git repository. I think that using Weblate would probably also > work, but I would like to enable that as a second step -- after the inclusion > of French. Ok for the direct git access. It could maybe be limited to some individuals while other team members could do MR. Direct access to teh git may be impressive to some people. Also OK to delay the integration of weblate until after the basis are there. > Once all this is done, the French translation would also automatically get > the latest changes of upstream manpages, so that the translation can be kept > up-to-date. The Debian packaging could also be adapted to generate packages > for French. > > I'll try to look into this in the next weeks, but I'll be on vacation in a > couple of weeks, so it might take some time. Ok. Tell us when we can do something. For now, the translations are still centralized on perkamon, where they were so far, so there is no rush on our side. I'm always super low on time but I may be able to help in the reorg of the packaging scripts, if you want. Thanks again for your generous offer and for your time. Mt. -- I wish I wasn't a co-author of this paper, I could have say what I really think of its quality. -- Bastard Professor From Hell signature.asc Description: PGP signature
Re: Status of manpages-fr -- help needed?
Am 5. Juli 2019 00:37:09 MESZ schrieb Martin Quinson : >Hello Tobias & Helge, > >I come back to you after your mail of Sun, 14 Oct 2018, offering your >help toward a better packaging of the manpage translations in French. >I am not subscribed on the dl10n-french list, so please keep me in CC. > >After some discussions, we think that it would indeed be a good thing >if we could merge our infrastructures. That is, if we could use your >infrastructure to host the french translations, please. > >As we (I) see it, we would benefit of your work to gather the english >version in an area where po4a is configured. Then we would push our >french translation, either directly in the git or with weblate or >similar. Then we would benefit from your packaging work, having timely >releases of the manpages uploaded to unstable. Am I right? Did I miss >something? > >Could you please point me again to where we should direct our MR? What >is your prefered workflow for this integration? And afterward for the >translation uploads? > >Thanks for the offer, >Mt Hi Martin, our offer still stands, we're happy to include the French translation in manpages-de. We should probably find a new name then. :-) However, I think that this will need some tweaks to our build system, so please allow me some time to adjust things. Or do you already have a MR ready? Regarding the workflow, I'd suggest that every French translator gets write access to the git repository. I think that using Weblate would probably also work, but I would like to enable that as a second step -- after the inclusion of French. Once all this is done, the French translation would also automatically get the latest changes of upstream manpages, so that the translation can be kept up-to-date. The Debian packaging could also be adapted to generate packages for French. I'll try to look into this in the next weeks, but I'll be on vacation in a couple of weeks, so it might take some time. Regards, Tobias
Re: Status of manpages-fr -- help needed?
Hello Tobias & Helge, I come back to you after your mail of Sun, 14 Oct 2018, offering your help toward a better packaging of the manpage translations in French. I am not subscribed on the dl10n-french list, so please keep me in CC. After some discussions, we think that it would indeed be a good thing if we could merge our infrastructures. That is, if we could use your infrastructure to host the french translations, please. As we (I) see it, we would benefit of your work to gather the english version in an area where po4a is configured. Then we would push our french translation, either directly in the git or with weblate or similar. Then we would benefit from your packaging work, having timely releases of the manpages uploaded to unstable. Am I right? Did I miss something? Could you please point me again to where we should direct our MR? What is your prefered workflow for this integration? And afterward for the translation uploads? Thanks for the offer, Mt -- If you can’t open it, you don’t own it. signature.asc Description: PGP signature
Re: Status of manpages-fr -- help needed?
Salut Thomas, Dixit Thomas Vincent, le 27/10/2018 : >Il y a aussi quelques Merge Requests en attente [1]. Est-ce la bonne >procédure ? Je t'ai ajouté comme Developper. Tu peux incorporer tes modifs, et/ou envoyer des demandes de relectures à la liste. Merci Baptiste
Re: Status of manpages-fr -- help needed?
Bonjour, Le 27/10/2018 à 15:36, Baptiste Jammet a écrit : > Je ne comprend pas… Tu as des traductions mises à jour ? > Si oui, tu peux pousser mais attention, perkamon/man-pages & > perkamon/man-pages-fr ont été mis à jour en version 4.16. Il y a aussi quelques Merge Requests en attente [1]. Est-ce la bonne procédure ? Amicalement, Thomas [1] https://gitlab.com/perkamon/man-pages-fr/merge_requests signature.asc Description: OpenPGP digital signature
Re: Status of manpages-fr -- help needed?
Bonjour, Dixit Jean-Baptiste Holcroft, le 27/10/2018 : >Hello Baptiste, is it helpful if I fulfil the translation and send >them to gitlab or should I wait? Je ne comprend pas… Tu as des traductions mises à jour ? Si oui, tu peux pousser mais attention, perkamon/man-pages & perkamon/man-pages-fr ont été mis à jour en version 4.16. Baptiste
Re: Status of manpages-fr -- help needed?
Le 19/10/2018 à 14:09, Baptiste Jammet a écrit : Hello Helge, et al. First of all thanks for your offer, and sorry for my late (and maybe too long) answer. Hello Baptiste, is it helpful if I fulfil the translation and send them to gitlab or should I wait? -- Jean-Baptiste Holcroft
Re: Status of manpages-fr -- help needed?
Hello Helge, et al.
First of all thanks for your offer, and sorry for my late (and maybe too
long) answer.
I don't have any "let's do this" solution but I can quickly explain how
french translation was handled.
The perkamon/man-pages project [1] is used to handle the infrastructure,
sharable with any language.
Next, the perkamon/man-pages-fr [2] is used to translate the manpages,
distro-agnostic.
Finally comes Debian packaging, using perkamon as upstream.
[1] https://gitlab.com/perkamon/man-pages
[2] https://gitlab.com/perkamon/man-pages-fr
I became the de-facto perkamon (upstream) maintainer some month ago, and
I try to update it until 4.15. But I didn't (for the moment) move some
residual infra away from Alioth. Nor update the translations.
Baptiste Jammet did a work to move the content to gitlab:
https://gitlab.com/perkamon/man-pages-fr/
I did not move anything to Gitlab. I just took over the maintenance of
perkamon.
but me personally would like to keep the
translation on project infrastructure, not some "free" other service.
I totally agree. But for the moment, perkamon can be seen as upstream,
so there is no hurry to move it to Salsa (which I would prefer btw).
I'm
willing to (learn how to) maintain this package and taffit kindly
agreed
to do the uploading magic (I'm a non-up DD).
If Thomas & taffit are ready to update the manpages-fr package, they
already could pull perkamon/man-pages-fr as of 4.15.
If not, I will be happy to have some help in the packaging, as I don't
have enough time for this at the moment.
For info, there is an archived repos of (the packaging of)
manpages-fr{,-extra} in alioth-archive [3].
[3] https://alioth-archive.debian.org/git/pkg-manpages-fr/
Baptiste
Re: Status of manpages-fr -- help needed?
Le 17 octobre 2018 18:53:07 GMT+02:00, Helge Kreutzmann a écrit : >Great to get teams interconected. Well, depending on other "free" system isn't a risk at all. The tool can easily be replaced by manual usage of git, or any other translation platform. Would you also be OK to produce manpages-fr releases and produce Debian packages? I should be able to find someone for Fedora. I forgot to say your initiative is great, thank you! -- Jean-Baptiste Holcroft
Re: Status of manpages-fr -- help needed?
Hello, Le 14/10/2018 à 17:29, Helge Kreutzmann a écrit : > Hello, > I recently noticed that manpages-fr was removed from testing. I felt sad. > It appeared as if the reason was that the manpages were too outdated. > > When I pushed for proper manpages-de maintenance years ago I was always > inspired by the French effort and achievments. Thus I (in agreement with > manpages-de maintainer Tobias) would like to ask if we could help > having manpages-fr in Debians next stable release (and beyond)? Certainly! > > We are a very small team and we cannot work on the translation, but we > could offer an infrastructure which would keep the manpage translation > current, i.e. regularly updated and released. Of course, over time more > and more paragraphs would be replaced by an updated english version and > if the French percentage felt below < 80% then the man pages would not be > shipped. But those pages who are rather stable (and many are) would > continue to be shipped. (Of course, French translators would be > welcome to update the outdated strings as they see fit). > > If you are interested we could discuss moving over the current French > manpages to the salsa infrastructure of manpages-de. I haven't (yet) > looked at the build infrastructure of manpages-fr, how much work this > would cause, but I'm confindent that this is dooable. That would be awesome. As mentioned by Jean-Baptiste, the perkamon project usually handled the french translation of manpages as a cross-distro effort. We would need to figure out how to stay in sync so it can benefit everyone. > > Please keep Tobias (and me) in the CC loop for the discussion. I also > CC'ed the manpages-fr maintainers. According to #873266 and #832385, both maintainers are unavailable. I'm willing to (learn how to) maintain this package and taffit kindly agreed to do the uploading magic (I'm a non-up DD). Thanks a lot Helge and Tobias! Thomas signature.asc Description: OpenPGP digital signature
Re: Status of manpages-fr -- help needed?
Hello Jean-Baptiste, On Tue, Oct 16, 2018 at 11:43:48PM +0200, Jean-Baptiste Holcroft wrote: > Le 14/10/2018 à 17:29, Helge Kreutzmann a écrit : > although admiring Debian-l10n work, I'm not a Debian contributor, but we > have the same issue in Fedora (I'm part of Fedora translation teams). Great to get teams interconected. > manpages-fr content is quite old, and we discussed this issue in November > 2017. > > Baptiste Jammet did a work to move the content to gitlab: > https://gitlab.com/perkamon/man-pages-fr/ > > > As maintaining so many files over time is a huge burden (and follow-up is > difficult), I offered him to connect the repository to the translation > platform Weblate, but for personal reasons, it took me months to be > available to do this. What we (the -de team) can offer is exactly this: getting refreshes of the files on a semi regular basis. How the translation is updated (again) is still up to the respective team. For de we are quite fine with plain git access, but other means are possible. I cannot speak for Tobias, but me personally would like to keep the translation on project infrastructure, not some "free" other service. > I'm 100% sure I won't be able to assume responsibility be a package > maintainer (nor git maintainer). This is part would solved by our proposal (for Debian, at least). Greetings Helge -- Dr. Helge Kreutzmann deb...@helgefjell.de Dipl.-Phys. http://www.helgefjell.de/debian.php 64bit GNU powered gpg signed mail preferred Help keep free software "libre": http://www.ffii.de/ signature.asc Description: Digital signature
Re: Status of manpages-fr -- help needed?
Le 14/10/2018 à 17:29, Helge Kreutzmann a écrit : Hello, I recently noticed that manpages-fr was removed from testing. I felt sad. It appeared as if the reason was that the manpages were too outdated. Hello Helge, although admiring Debian-l10n work, I'm not a Debian contributor, but we have the same issue in Fedora (I'm part of Fedora translation teams). manpages-fr content is quite old, and we discussed this issue in November 2017. Baptiste Jammet did a work to move the content to gitlab: https://gitlab.com/perkamon/man-pages-fr/ As maintaining so many files over time is a huge burden (and follow-up is difficult), I offered him to connect the repository to the translation platform Weblate, but for personal reasons, it took me months to be available to do this. Anyway, I connected his work with my personal installation of Weblate in September and it works fine. Here is the result in Weblate: https://translate.holcroft.fr/projects/man-pages-fr/#components Here is one commit in Gitlab: https://gitlab.com/perkamon/man-pages-fr/commit/43ff6c466c8696db9b3bd7a26b2d10d9f8c0bc16 Note: this is a proof of concept, I did not try to complete any translation. Once in Weblate, adding a new language should be easy (yes, I think we should ease language addition over time). Setting per team process (reviewers roles) is possible. Free project hosting exists: http://hosted.weblate.org Issue: it makes one commit per component, and each component is a file in the repository ==> the first update work will create a lot of commits. I would love to be able to contribute to the revival of this project and would be happy to translate if Weblate is used. I'm 100% sure I won't be able to assume responsibility be a package maintainer (nor git maintainer). But I don't feel legitimate to take decisions alone, I would love to see Baptiste coming back, or having another contributors to speak their minds. -- Jean-Baptiste Holcroft
