[publican-list] [Bug 482784] RFE: Support refentry

bugzilla at redhat.com bugzilla at redhat.com
Tue Sep 8 23:31:14 UTC 2009


Please do not reply directly to this email. All additional
comments should be made in the comments box of this bug.


https://bugzilla.redhat.com/show_bug.cgi?id=482784





--- Comment #10 from Jeff Fearn <jfearn at redhat.com>  2009-09-08 19:31:13 EDT ---
Working of the latest upstream test version the following change set works as
expected; so I can't duplicate the error :(

Note I moved the offending xi:include below the para's to bypass the error.

$ svn diff -x -u
Index: en-US/Tapset_Reference_Guide.ent
===================================================================
--- en-US/Tapset_Reference_Guide.ent (revision 21821)
+++ en-US/Tapset_Reference_Guide.ent (working copy)
@@ -2,4 +2,6 @@
 <!ENTITY BOOKID "Tapset_Reference_Guide">
 <!ENTITY YEAR "2008">
 <!ENTITY RHEL "Red Hat Enterprise Linux 5">
-<!ENTITY APH "'">
\ No newline at end of file
+<!ENTITY APH "'">
+<!ENTITY HOLDER "Red Hat, Inc">
+
Index: en-US/Tapset_Reference_Guide.xml
===================================================================
--- en-US/Tapset_Reference_Guide.xml (revision 21821)
+++ en-US/Tapset_Reference_Guide.xml (working copy)
@@ -28,10 +28,6 @@
 <section id="format">
 <title>Tapset Name Format</title>

-<para>In this guide, tapset definitions appear in the following format:</para>
-
-<xi:include href="refentry-example.xml"
xmlns:xi="http://www.w3.org/2001/XInclude" />
-
 <para>
 The <replaceable>return</replaceable> field specifies what data type the
 tapset extracts and returns from the kernel during a probe (and thus,
@@ -48,6 +44,10 @@
 exit functions, and print functions.
 </para>

+<para>In this guide, tapset definitions appear in the following format:</para>
+
+<xi:include href="refentry-example.xml"
xmlns:xi="http://www.w3.org/2001/XInclude" />
+
 <!--
 <varlistentry>
 <term></term>

-- 
Configure bugmail: https://bugzilla.redhat.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.




More information about the publican-list mailing list