summaryrefslogtreecommitdiffstats
path: root/bin/xmlformat-fdp.conf
diff options
context:
space:
mode:
authorKarsten Wade <kwade@redhat.com>2006-01-16 14:53:22 +0000
committerKarsten Wade <kwade@redhat.com>2006-01-16 14:53:22 +0000
commitefc1e5c49270c853a91257f31719209a6abd4301 (patch)
tree396b799c187154a396903a42d900ca412ad88a50 /bin/xmlformat-fdp.conf
parente6938324ec225660d4e0c5ffa2454825a58068e2 (diff)
downloadfedora-doc-utils-efc1e5c49270c853a91257f31719209a6abd4301.zip
fedora-doc-utils-efc1e5c49270c853a91257f31719209a6abd4301.tar.gz
fedora-doc-utils-efc1e5c49270c853a91257f31719209a6abd4301.tar.xz
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.
Diffstat (limited to 'bin/xmlformat-fdp.conf')
-rw-r--r--bin/xmlformat-fdp.conf5
1 files changed, 5 insertions, 0 deletions
diff --git a/bin/xmlformat-fdp.conf b/bin/xmlformat-fdp.conf
index c1cd81f..e791bc8 100644
--- a/bin/xmlformat-fdp.conf
+++ b/bin/xmlformat-fdp.conf
@@ -65,6 +65,11 @@ trademark
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