Index: doc/po4a.7.pod =================================================================== RCS file: /cvsroot/po4a/po4a/doc/po4a.7.pod,v retrieving revision 1.35 diff -u -p -r1.35 po4a.7.pod --- doc/po4a.7.pod 27 Feb 2005 22:56:01 -0000 1.35 +++ doc/po4a.7.pod 24 May 2005 11:57:45 -0000 @@ -1029,10 +1029,10 @@ The main advantages of po4a over them ar =head2 Educating developers about translation -When you try to translate documentation or programs, you face three kind of +When you try to translate documentation or programs, you face three kinds of problems; linguistics (not everybody speaks two languages), technical (that's why po4a exists) and relational/human. Not all developers understand -the necessity of translating stuff. Even when good willed may ignore how to +the necessity of translating stuff. Even when good willed, they may ignore how to ease the work of translators. To help with that, po4a comes with lot of documentation which can be referred to. @@ -1043,7 +1043,7 @@ hardly speak, and help them dealing corr In the po4a project, translated documents are not source files anymore. Since sgml files are habitually source files, it's an easy mistake. That's why all -file present this header: +files present this header: | ***************************************************** @@ -1055,14 +1055,14 @@ file present this header: | for example), but store the po file used as source file by po4a-translate. | | In fact, consider this as a binary, and the po file as a regular source file: - | If the po get lost, keeping this translation up-to-date will be harder ;) + | If the po gets lost, keeping this translation up-to-date will be harder ;) Likewise, gettext's regular po files only need to be copied to the po/ directory. But B. The major risk here is that a developer erases the existing translation of his program with the translation of his documentation. (Both of them can't be stored in the same po file, because the program needs to install its -translation as mo file while the documentation only use its translation at +translation as an mo file while the documentation only uses its translation at compile time). That's why the po files produced by the po-debiandoc module contain the following header: @@ -1091,14 +1091,14 @@ contain the following header: =item * -The translations are not stored along with the original, which makes +The translations are not stored along with the original, which makes it possible to detect if translations become out of date. =item * The translations are stored in separate files from each other, which prevents -translators of different languages to interfere. Both when submitting their -patch or at the file encoding level. +translators of different languages from interfering, both when submitting +their patch and at the file encoding level. =item * @@ -1120,7 +1120,7 @@ file editor (like emacs' po mode, kbabel =item * -Gettext offers simple way to get statistics about what is done, what should +Gettext offers a simple way to get statistics about what is done, what should be reviewed and updated, and what is still to do. Some example can be found at those addresses: @@ -1163,7 +1163,7 @@ a UTF8 perl pragma and then recoding the but it's not done yet. We would also like to factorise some code (about file insertion) of the sgml -module back into the TransTractor so that all modules can benefit of this, +module back into the TransTractor so that all modules can benefit from this, but this is not user visible. =head1 AUTHORS Index: lib/Locale/Po4a/TransTractor.pm =================================================================== RCS file: /cvsroot/po4a/po4a/lib/Locale/Po4a/TransTractor.pm,v retrieving revision 1.65 diff -u -p -r1.65 TransTractor.pm --- lib/Locale/Po4a/TransTractor.pm 9 Apr 2005 10:02:01 -0000 1.65 +++ lib/Locale/Po4a/TransTractor.pm 24 May 2005 11:57:45 -0000 @@ -113,8 +113,8 @@ sub parse {} =head1 SYNOPSIS -The following example parses a list of paragraphs beginning with "

". For sake -of simplicity, we assume that the document is well formatted, ie that '

' +The following example parses a list of paragraphs beginning with "

". For the sake +of simplicity, we assume that the document is well formatted, i.e. that '

' tags are the only tags present, and that this tag is at the very beginning of each paragraph. @@ -152,7 +152,7 @@ of each paragraph. # Reinit the loop ($line,$lref)=$self->shiftline(); } - # Did not got a defined line? End of input file. + # Did not get a defined line? End of input file. return; } } @@ -233,7 +233,7 @@ extracted from the input document. =item addendum (@) -list of filenames where we should read the addenda from. +List of filenames where we should read the addenda from. =item addendum_charset ($) @@ -992,9 +992,9 @@ To address this problem, the only interf =over 2 -=item - +=item - -take an hash as po_in_name (a list per language) +take a hash as po_in_name (a list per language) =item -