[Po4a-commits] "po4a/doc po4a.7.pod,1.41,1.42"

[Nicolas FRANCOIS]

Update of /cvsroot/po4a/po4a/doc
In directory alioth:/tmp/cvs-serv16663/doc

Modified Files:
	po4a.7.pod 
Log Message:
Fix a typo in po4a(7): s/doc-XX.po/doc.XX.po/ for consistency. Thanks to
Helge Kreutzmann. Closes: #428193


Index: po4a.7.pod
===================================================================
RCS file: /cvsroot/po4a/po4a/doc/po4a.7.pod,v
retrieving revision 1.41
retrieving revision 1.42
diff -u -d -r1.41 -r1.42
--- po4a.7.pod	11 Jun 2006 21:31:57 -0000	1.41
+++ po4a.7.pod	6 Jul 2007 18:33:53 -0000	1.42
@@ -335,7 +335,7 @@
 For that, use the L<po4a-translate(1)> program like that (where XX is the
 language code):
 
-  $ po4a-translate -f <format> -m <master.doc> -p <doc-XX.po> -l <XX.doc>
+  $ po4a-translate -f <format> -m <master.doc> -p <doc.XX.po> -l <XX.doc>
 
 As before, E<lt>formatE<gt> is the format used in the E<lt>master.docE<gt> document. But
 this time, the po file provided with the -p flag is part of the input. This
@@ -410,7 +410,7 @@
 
 Once you have the old original again, the gettextization may be as easy as:
 
- $ po4a-gettextize -f <format> -m <old.original> -l <old.translation> -p <doc-XX.po>
+ $ po4a-gettextize -f <format> -m <old.original> -l <old.translation> -p <doc.XX.po>
 
 When you're lucky, that's it. You converted your old translation to po4a and
 can begin with the updating task right away. Just follow the procedure