[Po4a-commits] po4a/doc po4a.7.pod,1.33,1.34

[Danilo Piazzalunga]

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

Modified Files:
	po4a.7.pod 
Log Message:
  (documentation)
  * Fix some typos and spelling errors.
  (translations)
  * Regenerate po/bin/po4a.pot and po/pod/po4a-pod.pot.
  * Update the Italian program translation.


Index: po4a.7.pod
===================================================================
RCS file: /cvsroot/po4a/po4a/doc/po4a.7.pod,v
retrieving revision 1.33
retrieving revision 1.34
diff -u -d -r1.33 -r1.34
--- po4a.7.pod	7 Jan 2005 22:50:51 -0000	1.33
+++ po4a.7.pod	14 Feb 2005 23:19:24 -0000	1.34
@@ -91,16 +91,16 @@
 I like the idea of open-source software, making it possible for everybody to
 access to software and to their source code. But being French, I'm well
 aware that the licensing is not the only restriction to the openness of
-software: Non-translated free softwares are useless for non-English
-speakers, and we still have some work to make them available to really
+software: non-translated free software is useless for non-English
+speakers, and we still have some work to make it available to really
 everybody out there.
 
 The perception of this situation by the open-source actors did dramatically
-improved recently. We, as translators, won the first battle and convinced
+improve recently. We, as translators, won the first battle and convinced
 everybody of the translations' importance. But unfortunately, it was the easy
 part. Now, we have to do the job and actually translate all this stuff.
 
-Actually, the open-source software themselves benefit of a rather decent
+Actually, open-source software themselves benefit of a rather decent
 level of translation, thanks to the wonderful gettext tool suite. It is able
 to extract the strings to translate from the program, present a uniform
 format to translators, and then use the result of their works at run time to
@@ -108,7 +108,7 @@
 
 But the situation is rather different when it comes to documentation. Too
 often, the translated documentation is not visible enough (not distributed
-as a part of the program), only partial or, not up to date. This last
+as a part of the program), only partial, or not up to date. This last
 situation is by far the worst possible one. Outdated translation can reveal
 worse than no translation at all to the users by describing old program
 behavior which are not in use anymore.
@@ -154,7 +154,7 @@
 =head3 nroff
 
 The good old manual pages' format, used by so much programs out there. The
-po4a support is very welcome here since this format is somehow difficult to
+po4a support is very welcome here since this format is somewhat difficult to
 use and not really friendly to the newbies.
 
 =head3 pod
@@ -167,7 +167,7 @@
 
 =head3 sgml
 
-Even if somehow superseded by XML nowadays, this format is still used
+Even if somewhat superseded by XML nowadays, this format is still used
 rather often for documents which are more than a few screens long. It allows
 you to make complete books. Updating the translation of so long documents can
 reveal to be a real nightmare. diff reveals often useless when the original
@@ -395,7 +395,7 @@
 faster than translating everything again. I was able to gettextize the
 existing French translation of the Perl documentation in one day, even if
 things B<did> went wrong. That was more than two megabytes of text, and a
-new translation would have last months or more. 
+new translation would have lasted months or more. 
 
 Let me explain the basis of the procedure first and I will come back on
 hints to achieve it when the process goes wrong. To ease comprehension, the
@@ -435,7 +435,7 @@
 
 Remove all extra parts of the translations, such as the section in which you
 give the translator name and thank every people who contributed to the
-translation. Addendums, which are described in the next section, will allow
+translation. Addenda, which are described in the next section, will allow
 you to re-add them afterward.
 
 =item -
@@ -526,9 +526,9 @@
 
 Because of the gettext approach, doing this becomes more difficult in po4a
 than it was when simply editing a new file along the original one. But it
-remains possible, thanks to the so-called B<addendums>.
+remains possible, thanks to the so-called B<addenda>.
 
-It may help the comprehension to consider addendums as a sort of patches
+It may help the comprehension to consider addenda as a sort of patches
 applied to the localized document after processing. They are rather
 different from the usual patches (they have only one line of context, which
 can embed perl regular expression, and they can only add new text without
@@ -852,7 +852,7 @@
 =head2 Addendum: How does it work?
 
 Well, that's pretty easy here. The translated document is not written
-directly to disk, but kept in memory until all addendum are applied. The
+directly to disk, but kept in memory until all the addenda are applied. The
 algorithms involved here are rather straightforward. We look for a line
 matching the position regexp, and insert the addendum before it if we're in
 mode=before. If not, we search for the next line matching the boundary and
@@ -914,7 +914,7 @@
 =item *
 
 This approach is the one used by professional translators. I agree, that
-they have somehow different goals than open-source translators. The
+they have somewhat different goals than open-source translators. The
 maintenance is for example often less critical to them since the content
 changes rarely.
 
@@ -1136,7 +1136,7 @@
 
 =item *
 
-Addendum are ... strange at the first glance.
+Addenda are... strange at the first glance.
 
 =item *