<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40"><head><meta http-equiv=Content-Type content="text/html; charset=utf-8"><meta name=Generator content="Microsoft Word 15 (filtered medium)"><style><!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
{font-family:Verdana;
panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman",serif;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
span.EmailStyle17
{mso-style-type:personal;
font-family:"Calibri",sans-serif;
color:#1F497D;}
span.EmailStyle18
{mso-style-type:personal-reply;
font-family:"Calibri",sans-serif;
color:#1F497D;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
/* List Definitions */
@list l0
{mso-list-id:1831093960;
mso-list-template-ids:1194499200;}
@list l1
{mso-list-id:2046447312;
mso-list-template-ids:-1685042950;}
@list l1:level1
{mso-level-tab-stop:.5in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l1:level2
{mso-level-tab-stop:1.0in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l1:level3
{mso-level-tab-stop:1.5in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l1:level4
{mso-level-tab-stop:2.0in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l1:level5
{mso-level-tab-stop:2.5in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l1:level6
{mso-level-tab-stop:3.0in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l1:level7
{mso-level-tab-stop:3.5in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l1:level8
{mso-level-tab-stop:4.0in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l1:level9
{mso-level-tab-stop:4.5in;
mso-level-number-position:left;
text-indent:-.25in;}
ol
{margin-bottom:0in;}
ul
{margin-bottom:0in;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]--></head><body lang=EN-US link=blue vlink=purple><div class=WordSection1><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D'>After reading up a bit on Docbook, I have been away for a bit … it leads me to the question:<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D'>Which Docbook XSLs are you using to process the input? Are you using the v5 Docbook XSLs?<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D'>In reading the Docbook 5 documentation, it appears that the input is now in a default namespace and that is xmlns=<a href="http://docbook.org/ns/docbook">http://docbook.org/ns/docbook</a>.<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D'>So the v5 Docbook XSLs should account for this.<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D'>Which XSLs are you using?<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D'>Kevin<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D'><o:p> </o:p></span></p><div><div style='border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0in 0in 0in'><p class=MsoNormal><b><span style='font-size:11.0pt;font-family:"Calibri",sans-serif'>From:</span></b><span style='font-size:11.0pt;font-family:"Calibri",sans-serif'> Xep-support [mailto:xep-support-bounces@renderx.com] <b>On Behalf Of </b>Kevin Brown<br><b>Sent:</b> Thursday, May 03, 2018 11:14 AM<br><b>To:</b> 'RenderX Community Support List' <xep-support@renderx.com><br><b>Subject:</b> [xep-support] Re: line 1: Incorrect top element - should be 'root'<o:p></o:p></span></p></div></div><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D'>NOTE: You can just create a simple bat/sh file to run Saxon.jar and input your XML and the XSL you are using.<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D'>Saxon.jar would be in the XEP installation directory … this is the same as you did with xsltproc.<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D'>Saxon (likely) is giving you the correct answer, there is no match. I do not see your Docbook XSLs but I suspect there is no namespace in them if they are vanilla.<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D'>Take this very simple example:<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D'>XML is:<o:p></o:p></span></p><p class=MsoNormal style='background:white;text-autospace:none'><span style='color:#000096;background:white;mso-highlight:white'><foo></foo></span><span style='background:white;mso-highlight:white'><o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D'>XSL is:<o:p></o:p></span></p><p class=MsoNormal style='background:white;text-autospace:none'><span style='color:#005AB4;background:white;mso-highlight:white'><xsl:stylesheet</span><span style='color:#F5844C;background:white;mso-highlight:white'> </span><span style='color:#0099CC;background:white;mso-highlight:white'>xmlns:xsl</span><span style='color:#FF8040;background:white;mso-highlight:white'>=</span><span style='color:#993300;background:white;mso-highlight:white'>"</span><a href="http://www.w3.org/1999/XSL/Transform"><span style='background:white;mso-highlight:white'>http://www.w3.org/1999/XSL/Transform</span></a><span style='color:#993300;background:white;mso-highlight:white'>"</span><span style='color:#F5844C;background:white;mso-highlight:white'> version</span><span style='color:#FF8040;background:white;mso-highlight:white'>=</span><span style='color:#993300;background:white;mso-highlight:white'>"1.0"</span><span style='color:#000096;background:white;mso-highlight:white'>></span><span style='color:black;background:white;mso-highlight:white'><br> </span><span style='color:#005AB4;background:white;mso-highlight:white'><xsl:template</span><span style='color:#F5844C;background:white;mso-highlight:white'> match</span><span style='color:#FF8040;background:white;mso-highlight:white'>=</span><span style='color:#993300;background:white;mso-highlight:white'>"foo"</span><span style='color:#000096;background:white;mso-highlight:white'>></span><span style='color:black;background:white;mso-highlight:white'><br> </span><span style='color:#000096;background:white;mso-highlight:white'><bar/></span><span style='color:black;background:white;mso-highlight:white'><br> </span><span style='color:#005AB4;background:white;mso-highlight:white'></xsl:template></span><span style='color:black;background:white;mso-highlight:white'><br></span><span style='color:#005AB4;background:white;mso-highlight:white'></xsl:stylesheet></span><span style='background:white;mso-highlight:white'><o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D'>Output is:<o:p></o:p></span></p><p class=MsoNormal style='background:white;text-autospace:none'><span style='color:#000096;background:white;mso-highlight:white'><bar/></span><span style='background:white;mso-highlight:white'><o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal style='background:white;text-autospace:none'><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D'>But change the input to:<br></span><span style='color:#000096;background:white;mso-highlight:white'><foo</span><span style='color:#F5844C;background:white;mso-highlight:white'> xmlns</span><span style='color:#FF8040;background:white;mso-highlight:white'>=</span><span style='color:#993300;background:white;mso-highlight:white'>"</span><a href="http://docbook.org/ns/docbook"><span style='background:white;mso-highlight:white'>http://docbook.org/ns/docbook</span></a><span style='color:#993300;background:white;mso-highlight:white'>"</span><span style='color:#000096;background:white;mso-highlight:white'>></foo></span><span style='background:white;mso-highlight:white'><o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D'>Output is nothing. <o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D'>Why? Because </span><span style='color:#000096;background:white;mso-highlight:white'><foo</span><span style='color:#F5844C;background:white;mso-highlight:white'> xmlns</span><span style='color:#FF8040;background:white;mso-highlight:white'>=</span><span style='color:#993300;background:white;mso-highlight:white'>"</span><a href="http://docbook.org/ns/docbook"><span style='background:white;mso-highlight:white'>http://docbook.org/ns/docbook</span></a><span style='color:#993300;background:white;mso-highlight:white'>"</span><span style='color:#000096;background:white;mso-highlight:white'>></foo></span><span style='color:#000096'> is not matched by the template </span><span style='color:#005AB4;background:white;mso-highlight:white'><xsl:template</span><span style='color:#F5844C;background:white;mso-highlight:white'> match</span><span style='color:#FF8040;background:white;mso-highlight:white'>=</span><span style='color:#993300;background:white;mso-highlight:white'>"foo"</span><span style='color:#000096;background:white;mso-highlight:white'>><bar/></span><span style='color:#005AB4;background:white;mso-highlight:white'></xsl:template></span><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D'><o:p></o:p></span></p><p class=MsoNormal><b><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D'><o:p> </o:p></span></b></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D'>There is no template matching foo in the namespace specified.<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D'>The stackoverflow article gives various guidance like changing the XSLs to 2.0 and adding that namespace or a whole sale rewrite of the template to add a prefixed namespace that equates to the default one in your XML. <o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D'>The best solution is to figure out how/why the process producing the XML is adding that namespace, it should not really. Docbook XML AFAIK should have no namespace.<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D'>Kevin Brown<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D'>RenderX<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D'><o:p> </o:p></span></p><div><div style='border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0in 0in 0in'><p class=MsoNormal><b><span style='font-size:11.0pt;font-family:"Calibri",sans-serif'>From:</span></b><span style='font-size:11.0pt;font-family:"Calibri",sans-serif'> Xep-support [</span><a href="mailto:xep-support-bounces@renderx.com"><span style='font-size:11.0pt;font-family:"Calibri",sans-serif'>mailto:xep-support-bounces@renderx.com</span></a><span style='font-size:11.0pt;font-family:"Calibri",sans-serif'>] <b>On Behalf Of </b>Kevin Brown<br><b>Sent:</b> Thursday, May 03, 2018 10:11 AM<br><b>To:</b> RenderX Community Support List <</span><a href="mailto:xep-support@renderx.com"><span style='font-size:11.0pt;font-family:"Calibri",sans-serif'>xep-support@renderx.com</span></a><span style='font-size:11.0pt;font-family:"Calibri",sans-serif'>><br><b>Subject:</b> [xep-support] Re: line 1: Incorrect top element - should be 'root'<o:p></o:p></span></p></div></div><p class=MsoNormal><o:p> </o:p></p><div><p class=MsoNormal>Please read this excellent post on Stackoverflow.<o:p></o:p></p></div><div><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal><a href="https://stackoverflow.com/questions/1344158/xslt-with-xml-source-that-has-a-default-namespace-set-to-xmlns">https://stackoverflow.com/questions/1344158/xslt-with-xml-source-that-has-a-default-namespace-set-to-xmlns</a><o:p></o:p></p></div><div><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal>X4U is not doing anything except processing the results of Saxon transform which is nothing. The namespace is your XML does not match anything in the XSLT.<o:p></o:p></p></div><div><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal>Kevin<o:p></o:p></p></div><div><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal><o:p> </o:p></p></div><div id="composer_signature"><div><p class=MsoNormal><span style='font-size:10.0pt;color:#575757'>Sent from my Verizon, Samsung Galaxy smartphone<o:p></o:p></span></p></div></div><div><p class=MsoNormal><o:p> </o:p></p></div><div><div><p class=MsoNormal><span style='color:black'>-------- Original message --------<o:p></o:p></span></p></div><div><p class=MsoNormal><span style='color:black'>From: Stephen Taylor <</span><a href="mailto:stephen@kx.com">stephen@kx.com</a><span style='color:black'>> <o:p></o:p></span></p></div><div><p class=MsoNormal><span style='color:black'>Date: 5/3/18 1:08 AM (GMT-08:00) <o:p></o:p></span></p></div><div><p class=MsoNormal><span style='color:black'>To: XEP Support <</span><a href="mailto:xep-support@renderx.com">xep-support@renderx.com</a><span style='color:black'>> <o:p></o:p></span></p></div><div><p class=MsoNormal><span style='color:black'>Subject: [xep-support] Re: line 1: Incorrect top element - should be 'root' <o:p></o:p></span></p></div><div><p class=MsoNormal><span style='color:black'><o:p> </o:p></span></p></div></div><div><p class=MsoNormal>That would be consistent with the following experiment. If I take the XML in its ‘working’ form and change the root element from <span style='font-family:"Courier New"'>article</span><span style='font-family:"Arial",sans-serif'> to </span><span style='font-family:"Courier New"'>book</span><span style='font-family:"Arial",sans-serif'> I get the same error message. </span><o:p></o:p></p><div><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal><span style='font-family:"Arial",sans-serif'>However, using </span><span style='font-family:"Courier New"'>xsltproc</span><span style='font-family:"Arial",sans-serif'> for the initial XSLT from XML (</span><span style='font-family:"Courier New"'>xmlns</span><span style='font-family:"Arial",sans-serif'> attribute included) produces valid FO XML:</span><o:p></o:p></p></div><div><p class=MsoNormal><o:p> </o:p></p></div><div><div><p class=MsoNormal><span style='font-family:"Courier New"'><?xml version="1.0"?></span><o:p></o:p></p></div><div><p class=MsoNormal><span style='font-family:"Courier New"'><fo:root xmlns:fo="</span><a href="http://www.w3.org/1999/XSL/Format" target="_blank"><span style='font-family:"Courier New"'>http://www.w3.org/1999/XSL/Format</span></a><span style='font-family:"Courier New"'>" xmlns:xlink="</span><a href="http://www.w3.org/1999/xlink" target="_blank"><span style='font-family:"Courier New"'>http://www.w3.org/1999/xlink</span></a><span style='font-family:"Courier New"'>"><fo:layout-master-set><fo:simple-page-master master-name="cover-page" page-width="210mm" …</span><o:p></o:p></p></div><div><p class=MsoNormal><span style='font-family:"Arial",sans-serif'><o:p> </o:p></span></p></div><div><p class=MsoNormal><span style='font-family:"Arial",sans-serif'>which </span><span style='font-family:"Courier New"'>x4u</span><span style='font-family:"Arial",sans-serif'> renders happily to PDF.</span><o:p></o:p></p></div><div><p class=MsoNormal><span style='font-family:"Arial",sans-serif'><o:p> </o:p></span></p></div><div><p class=MsoNormal><span style='font-family:"Arial",sans-serif'>That suggests the answer to my question <i>Is there a better solution to this than removing the attribute? </i> might be: Yes, use </span><span style='font-family:"Courier New"'>xsltproc</span><span style='font-family:"Arial",sans-serif'> for the initial transform to FO. Hard to imagine RenderX being satisfied with this answer, though. </span><o:p></o:p></p></div><div><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal><span style='font-family:"Arial",sans-serif'>Let me also draw your attention to the error report from </span><span style='font-family:"Courier New"'>x4u</span><span style='font-family:"Arial",sans-serif'>:</span><o:p></o:p></p></div><div><p class=MsoNormal><o:p> </o:p></p></div><div><div><p class=MsoNormal><span style='font-family:"Courier New"'>(document [system-id file:/Users/sjt/Projects/kx/tmp/aws/aws.xml]</span><o:p></o:p></p></div><div><p class=MsoNormal><span style='font-family:"Courier New"'> (validate </span><o:p></o:p></p></div><div><p class=MsoNormal><span style='font-family:"Courier New"'> [error] file:/Users/sjt/Projects/kx/tmp/aws/aws.xml: line 1: Incorrect top element - should be 'root'</span><o:p></o:p></p></div><div><p class=MsoNormal><span style='font-family:"Courier New"'> [validation total: 1 error]</span><o:p></o:p></p></div><div><p class=MsoNormal><span style='font-family:"Courier New"'> [error] com.renderx.xep.lib.FormatterException: Invalid XSL FO source 'file:/Users/sjt/Projects/kx/tmp/aws/aws.xml': 1 error found during validation</span><o:p></o:p></p></div><div><p class=MsoNormal><span style='font-family:"Courier New"'> [error] javax.xml.transform.TransformerException: com.renderx.xep.lib.FormatterException: Invalid XSL FO source 'file:/Users/sjt/Projects/kx/tmp/aws/aws.xml': 1 error found during validation</span><o:p></o:p></p></div><div><p class=MsoNormal><span style='font-family:"Courier New"'> [error] formatting failed</span><o:p></o:p></p></div><div><p class=MsoNormal><span style='font-family:"Courier New"'> [error] javax.xml.transform.TransformerException: com.renderx.xep.lib.FormatterException: Invalid XSL FO source 'file:/Users/sjt/Projects/kx/tmp/aws/aws.xml': 1 error found during validation</span><o:p></o:p></p></div><div><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal><span style='font-family:"Courier New"'>Formatting failed</span><o:p></o:p></p></div><div><p class=MsoNormal><span style='font-family:"Arial",sans-serif'><o:p> </o:p></span></p></div></div><div><p class=MsoNormal><span style='font-family:"Arial",sans-serif'>We suppose the error to be in the FO produced by the initial transform. Above it is reported helpfully as </span><span style='font-family:"Courier New"'>Invalid XSL FO source</span><span style='font-family:"Arial",sans-serif'> but misleadingly as a validation error in line 1 of the original XML source. </span><o:p></o:p></p></div><div><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal><span style='font-family:"Arial",sans-serif'>That would of course be the place to point if no stylesheet were being applied. But </span><span style='font-family:"Courier New"'>x4u</span><span style='font-family:"Arial",sans-serif'> knows better.</span><o:p></o:p></p></div><div><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal><span style='font-family:"Arial",sans-serif'>What would I want </span><span style='font-family:"Courier New"'>x4u</span><span style='font-family:"Arial",sans-serif'> to do here? Write the intermediate FO to a temporary file and report the validation error in that. In this case the error seems to be in XEP’s XSLT processor, but if my XSL had produced invalid FO it would be helpful to see it. </span><o:p></o:p></p></div><div><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal><span style='font-family:"Arial",sans-serif'>Which leaves questions:</span><o:p></o:p></p><div><ol start=1 type=1><li class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l1 level1 lfo3'><span style='font-family:"Arial",sans-serif'>Why does </span><span style='font-family:"Courier New"'>x4u</span><span style='font-family:"Arial",sans-serif'> choke on the </span><span style='font-family:"Courier New"'>xmlns</span><span style='font-family:"Arial",sans-serif'> attribute?</span><o:p></o:p></li><li class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l1 level1 lfo3'><span style='font-family:"Arial",sans-serif'>Is there a better solution than (a) removing the attribute or (b) avoiding the XEP XSLT processor for the transformation to FO?</span><o:p></o:p></li></ol><div><p class=MsoNormal>Stephen<br clear=all><o:p></o:p></p><div><div><div><div><div><div><div><p class=MsoNormal><o:p> </o:p></p><div><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal><span style='font-size:7.5pt;font-family:"Verdana",sans-serif'>Stephen Taylor | Librarian | <b><span style='color:#3D85C6'>Kx</span></b> | +44 7713 400852 | </span><a href="mailto:stephen@kx.com" target="_blank"><span style='font-size:7.5pt;font-family:"Verdana",sans-serif'>stephen@kx.com</span></a><o:p></o:p></p></div></div></div></div></div></div></div></div><p class=MsoNormal><o:p> </o:p></p><div><p class=MsoNormal>On 2 May 2018 at 20:00, <<a href="mailto:xep-support-request@renderx.com" target="_blank">xep-support-request@renderx.com</a>> wrote:<o:p></o:p></p><blockquote style='border:none;border-left:solid #CCCCCC 1.0pt;padding:0in 0in 0in 6.0pt;margin-left:4.8pt;margin-top:5.0pt;margin-right:0in;margin-bottom:5.0pt'><p class=MsoNormal>Send Xep-support mailing list submissions to<br> <a href="mailto:xep-support@renderx.com" target="_blank">xep-support@renderx.com</a><br><br>To subscribe or unsubscribe via the World Wide Web, visit<br> <a href="http://lists.renderx.com/mailman/listinfo/xep-support" target="_blank">http://lists.renderx.com/mailman/listinfo/xep-support</a><br>or, via email, send a message with subject or body 'help' to<br> <a href="mailto:xep-support-request@renderx.com" target="_blank">xep-support-request@renderx.com</a><br><br>You can reach the person managing the list at<br> <a href="mailto:xep-support-owner@renderx.com" target="_blank">xep-support-owner@renderx.com</a><br><br>When replying, please edit your Subject line so it is more specific<br>than "Re: Contents of Xep-support digest..."<br><br><br>Today's Topics:<br><br> 1. Re: Xep-support Digest, Vol 86, Issue 1 (Kevin Brown)<br><br><br>----------------------------------------------------------------------<br><br>Message: 1<br>Date: Tue, 1 May 2018 14:44:21 -0700<br>From: "Kevin Brown" <<a href="mailto:kevin@renderx.com" target="_blank">kevin@renderx.com</a>><br>To: "'RenderX Community Support List'" <<a href="mailto:xep-support@renderx.com" target="_blank">xep-support@renderx.com</a>><br>Subject: [xep-support] Re: Xep-support Digest, Vol 86, Issue 1<br>Message-ID: <001801d3e195$92c447b0$b84cd710$@<a href="http://renderx.com" target="_blank">renderx.com</a>><br>Content-Type: text/plain; charset="utf-8"<br><br>In other words:<br><br><br><br><article xmlns=?<a href="http://docbook.org/ns/docbook" target="_blank">http://docbook.org/ns/docbook</a>?><br><br><br><br>Does not match:<br><br><article><br><br><br><br>Kevin<br><br><br><br>From: Xep-support [mailto:<a href="mailto:xep-support-bounces@renderx.com" target="_blank">xep-support-bounces@renderx.com</a>] On Behalf Of Stephen Taylor<br>Sent: Tuesday, May 01, 2018 2:14 PM<br>To: XEP Support <<a href="mailto:xep-support@renderx.com" target="_blank">xep-support@renderx.com</a>><br>Subject: [xep-support] Re: Xep-support Digest, Vol 86, Issue 1<br><br><br><br>Sorry I did not make myself more clear. <br><br><br><br>x4u renders my XML and XSL as a PDF ? 70 pages of beautiful typography ? provided I remove the xmlns attribute from the XML root element, which is, as you note, article. <br><br><br><br>The xmlns attribute was written by Pandoc <<a href="http://pandoc.org" target="_blank">http://pandoc.org</a>> as DocBook 5 <<a href="http://docbook.org" target="_blank">http://docbook.org</a>> XML output. It looks correct to me. DocBook is an XML application that will be familiar to many XEP users. So I?m wondering why x4u would report the attribute as a validation error in the XML. <br><br><br><br>My question stands: is there a better solution to this than removing the attribute? <o:p></o:p></p></blockquote></div></div></div></div></div></div></div></body></html>