Update of /cvsroot/po4a/po4a
In directory haydn:/tmp/cvs-serv9566
Modified Files:
po4a po4a-gettextize po4a-normalize po4a-translate
po4a-updatepo
Log Message:
Standarized the project goal description.
Also updated po/pod/* to reflect this change and to adapt to the new file
sorting from Build.PL.
Sorry for the big diff :(
Index: po4a-normalize
===================================================================
RCS file: /cvsroot/po4a/po4a/po4a-normalize,v
retrieving revision 1.16
retrieving revision 1.17
diff -u -d -r1.16 -r1.17
--- po4a-normalize 18 Jul 2004 05:13:24 -0000 1.16
+++ po4a-normalize 19 Jul 2004 10:21:12 -0000 1.17
@@ -23,8 +23,8 @@
=head1 DESCRIPTION
The po4a (po for anything) project goal is to ease translations (and more
-interstingly, the maintenance of translation) using gettext tools on areas
-where they were not expected like documentation.
+interestingly, the maintenance of translations) using gettext tools on
+areas where they were not expected like documentation.
The C<po4a-normalize> script is a debugging tool used to make sure that
po4a don't change the document when it's not supposed to. Only use it if
Index: po4a-translate
===================================================================
RCS file: /cvsroot/po4a/po4a/po4a-translate,v
retrieving revision 1.24
retrieving revision 1.25
diff -u -d -r1.24 -r1.25
--- po4a-translate 18 Jul 2004 08:47:22 -0000 1.24
+++ po4a-translate 19 Jul 2004 10:21:12 -0000 1.25
@@ -25,8 +25,8 @@
=head1 DESCRIPTION
The po4a (po for anything) project goal is to ease translations (and more
-interstingly, the maintenance of translation) using gettext tools on areas
-where they were not expected like documentation.
+interestingly, the maintenance of translations) using gettext tools on
+areas where they were not expected like documentation.
The C<po4a-translate> script is in charge of converting the translation
(which were done in a po file) under the documentation format back. The
Index: po4a
===================================================================
RCS file: /cvsroot/po4a/po4a/po4a,v
retrieving revision 1.10
retrieving revision 1.11
diff -u -d -r1.10 -r1.11
--- po4a 18 Jul 2004 08:42:53 -0000 1.10
+++ po4a 19 Jul 2004 10:21:12 -0000 1.11
@@ -23,8 +23,8 @@
=head1 DESCRIPTION
The po4a (po for anything) project goal is to ease translations (and more
-interstingly, the maintenance of translation) using gettext tools on areas
-where they were not expected like documentation.
+interestingly, the maintenance of translations) using gettext tools on
+areas where they were not expected like documentation.
The C<po4a> program is in charge of updating both the po files (to sync
them to the original documents) and the translated documents (to sync
Index: po4a-updatepo
===================================================================
RCS file: /cvsroot/po4a/po4a/po4a-updatepo,v
retrieving revision 1.21
retrieving revision 1.22
diff -u -d -r1.21 -r1.22
--- po4a-updatepo 18 Jul 2004 05:13:24 -0000 1.21
+++ po4a-updatepo 19 Jul 2004 10:21:12 -0000 1.22
@@ -25,8 +25,8 @@
=head1 DESCRIPTION
The po4a (po for anything) project goal is to ease translations (and more
-interstingly, the maintenance of translation) using gettext tools on areas
-where they were not expected like documentation.
+interestingly, the maintenance of translations) using gettext tools on
+areas where they were not expected like documentation.
The C<po4a-updatepo> script is in charge of updating po files to make
them reflect the changes made to the original documentation file. For that,
Index: po4a-gettextize
===================================================================
RCS file: /cvsroot/po4a/po4a/po4a-gettextize,v
retrieving revision 1.21
retrieving revision 1.22
diff -u -d -r1.21 -r1.22
--- po4a-gettextize 18 Jul 2004 05:13:24 -0000 1.21
+++ po4a-gettextize 19 Jul 2004 10:21:12 -0000 1.22
@@ -25,8 +25,8 @@
=head1 DESCRIPTION
The po4a (po for anything) project goal is to ease translations (and more
-interstingly, the maintenance of translation) using gettext tools on areas
-where they were not expected like documentation.
+interestingly, the maintenance of translations) using gettext tools on
+areas where they were not expected like documentation.
The C<po4a-gettextize> script is in charge of converting documentation
files to po files. If you start a new translation, C<po4a-gettextize>