[Po4a-devel][CVS po4a]po4a/po/pod fr.po,1.22,1.23 po4a-pod.pot,1.21,1.22

Denis Barbier po4a-devel@lists.alioth.debian.org
Wed, 28 Apr 2004 21:36:34 +0000


Update of /cvsroot/po4a/po4a/po/pod
In directory haydn:/tmp/cvs-serv28080/po/pod

Modified Files:
	fr.po po4a-pod.pot 
Log Message:
s/repport/report/


Index: po4a-pod.pot
===================================================================
RCS file: /cvsroot/po4a/po4a/po/pod/po4a-pod.pot,v
retrieving revision 1.21
retrieving revision 1.22
diff -u -d -r1.21 -r1.22
--- po4a-pod.pot	28 Apr 2004 09:58:59 -0000	1.21
+++ po4a-pod.pot	28 Apr 2004 21:36:32 -0000	1.22
@@ -384,7 +384,7 @@
 "msgid as msgstr. To make sure that things get ok, each msgid in po objects "
 "are given a type, based on their structure (like \"chapt\", \"sect1\", \"p\" "
 "and so on in docbook). If the types of strings are not the same, that mean "
-"that both files do not share the same structure, and the process repports an "
+"that both files do not share the same structure, and the process reports an "
 "error."
 msgstr ""
 
@@ -1805,7 +1805,7 @@
 "In most cases, po4a::man will detect the problem and refuse to process the "
 "page, issuing an adapted message. In some rare cases, the program will "
 "complete without warning, but the output will be wrong. Such cases are "
-"called \"bugs\" ;) If you encounter such case, be sure to repport this, "
+"called \"bugs\" ;) If you encounter such case, be sure to report this, "
 "along with a fix when possible..."
 msgstr ""
 
@@ -2227,9 +2227,9 @@
 #: ../../po4a-gettextize:41
 msgid ""
 "However, C<po4a-gettextize> will diagnose your death by detecting any "
-"desyncronisation between files, and repporting where they occur. In that "
-"case, you should edit manually the files to solve the repported disparity. "
-"Even if no error were repported, you check carefully that the generated po "
+"desyncronisation between files, and reporting where they occur. In that "
+"case, you should edit manually the files to solve the reported disparity. "
+"Even if no error were reported, you check carefully that the generated po "
 "file is correct (ie, that each msgstr is the translation of the associated "
 "msgid, and not the one before or after)."
 msgstr ""

Index: fr.po
===================================================================
RCS file: /cvsroot/po4a/po4a/po/pod/fr.po,v
retrieving revision 1.22
retrieving revision 1.23
diff -u -d -r1.22 -r1.23
--- fr.po	28 Apr 2004 10:05:50 -0000	1.22
+++ fr.po	28 Apr 2004 21:36:32 -0000	1.23
@@ -403,7 +403,7 @@
 "msgid as msgstr. To make sure that things get ok, each msgid in po objects "
 "are given a type, based on their structure (like \"chapt\", \"sect1\", \"p\" "
 "and so on in docbook). If the types of strings are not the same, that mean "
-"that both files do not share the same structure, and the process repports an "
+"that both files do not share the same structure, and the process reports an "
 "error."
 msgstr ""
 "Il s'agit principalement d'un argument interne utilisé lors de la "
@@ -1748,7 +1748,7 @@
 "In most cases, po4a::man will detect the problem and refuse to process the "
 "page, issuing an adapted message. In some rare cases, the program will "
 "complete without warning, but the output will be wrong. Such cases are "
-"called \"bugs\" ;) If you encounter such case, be sure to repport this, "
+"called \"bugs\" ;) If you encounter such case, be sure to report this, "
 "along with a fix when possible..."
 msgstr ""
 
@@ -2192,9 +2192,9 @@
 #: ../../po4a-gettextize:41
 msgid ""
 "However, C<po4a-gettextize> will diagnose your death by detecting any "
-"desyncronisation between files, and repporting where they occur. In that "
-"case, you should edit manually the files to solve the repported disparity. "
-"Even if no error were repported, you check carefully that the generated po "
+"desyncronisation between files, and reporting where they occur. In that "
+"case, you should edit manually the files to solve the reported disparity. "
+"Even if no error were reported, you check carefully that the generated po "
 "file is correct (ie, that each msgstr is the translation of the associated "
 "msgid, and not the one before or after)."
 msgstr ""