[Po4a-commits] po4a/doc po4a.7.pod,1.35,1.36

[Martin Quinson]

Update of /cvsroot/po4a/po4a/doc
In directory haydn:/tmp/cvs-serv5189/doc

Modified Files:
	po4a.7.pod 
Log Message:
Documentation improvements [Francois Gouget]

Index: po4a.7.pod
===================================================================
RCS file: /cvsroot/po4a/po4a/doc/po4a.7.pod,v
retrieving revision 1.35
retrieving revision 1.36
diff -u -d -r1.35 -r1.36
--- po4a.7.pod	27 Feb 2005 22:56:01 -0000	1.35
+++ po4a.7.pod	25 May 2005 17:05:05 -0000	1.36
@@ -1029,10 +1029,10 @@
 
 =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 @@
 
 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 @@
  | 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<this is not the case of the ones manipulated by po4a>. 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 @@
 
 =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 @@
 
 =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 @@
 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