[Po4a-commits] "po4a/doc po4a.7.pod,1.50,1.51"

[Denis Barbier]

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

Modified Files:
	po4a.7.pod 
Log Message:
Fix Debian bug 563541: format type mismatch between manual page and real command


Index: po4a.7.pod
===================================================================
RCS file: /cvsroot/po4a/po4a/doc/po4a.7.pod,v
retrieving revision 1.50
retrieving revision 1.51
diff -u -d -r1.50 -r1.51
--- po4a.7.pod	14 Jan 2010 22:03:00 -0000	1.50
+++ po4a.7.pod	30 Jan 2010 09:34:58 -0000	1.51
@@ -146,7 +146,7 @@
 Currently, this approach has been successfully implemented to several kinds
 of text formatting formats:
 
-=head3 nroff
+=head3 man
 
 The good old manual pages' format, used by so much programs out there. The
 po4a support is very welcome here since this format is somewhat difficult to
@@ -476,7 +476,7 @@
 =item - 
 
 Sometimes, the paragraph content does match, but their types don't. Fixing it
-is rather format-dependant. In pod and nroff, it often comes from the fact
+is rather format-dependant. In pod and man, it often comes from the fact
 that one of the two contains a line beginning with a white space where the
 other doesn't. In those formats, such paragraph cannot be wrapped and thus
 become a different type. Just remove the space and you are fine. It may also
@@ -633,7 +633,7 @@
 Both forms exist because documentation formats are different. In some of
 them, there is a way to mark the end of a section (just like the
 C<E<lt>/sectionE<gt>> we just used), while some other don't explicitly mark
-the end of section (like in nroff). In the former case, you want to make a
+the end of section (like in man). In the former case, you want to make a
 I<boundary> matching the I<end of a section>, so that the I<insertion point>
 comes after it. In the latter case, you want to make a I<boundary> matching
 the I<beginning of next section>, so that the I<insertion point> comes just