[Date Prev][Date Next] [Thread Prev][Thread Next]
[Thread Index]
[Date Index]
[Author Index]
docs-common/bin xmlformat-fdp.conf,1.12,1.13
- From: "Karsten Wade" (kwade) <fedora-docs-commits redhat com>
- To: fedora-docs-commits redhat com
- Subject: docs-common/bin xmlformat-fdp.conf,1.12,1.13
- Date: Mon, 16 Jan 2006 09:53:30 -0500
Author: kwade
Update of /cvs/docs/docs-common/bin
In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv27478
Modified Files:
xmlformat-fdp.conf
Log Message:
Need to mark the table's entry out separately, because it is not possible to predict what is needed. The parser looks to the existence of any whitespace after the <entry> as an indication of inline v. block markup, and there is no way to tell with xmlformat. It is better to leave this alone and to the discretion of the author to solve. The problem to solve next is, what happens when xmlformat encounters content on the same line as <entry>. I'll test later.
Index: xmlformat-fdp.conf
===================================================================
RCS file: /cvs/docs/docs-common/bin/xmlformat-fdp.conf,v
retrieving revision 1.12
retrieving revision 1.13
diff -u -r1.12 -r1.13
--- xmlformat-fdp.conf 16 Jan 2006 13:15:33 -0000 1.12
+++ xmlformat-fdp.conf 16 Jan 2006 14:53:22 -0000 1.13
@@ -65,6 +65,11 @@
screen programlisting
format = verbatim
+# <entry> is special because a linebreak has meaning, best leave the
+# decisions up to the experts
+entry
+ format = verbatim
+
command application filename option userinput computeroutput replaceable
format = inline
[Date Prev][Date Next] [Thread Prev][Thread Next]
[Thread Index]
[Date Index]
[Author Index]