[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: Re: [docbook] Strange HTML output...
j3d On 02.12.2011 06:30, Mark Craig wrote:
Hello, When I add ${basedir}/generated to the docbkx-tools configuration, and then run the stylesheet for HTML directly on the result, I get lots of "no template matches" errors. And the output looks almost identical. $ xsltproc ~/Documents/docbook/html/docbook.xsl generated/(gen)csharp-coding-guidelines.xml > csharp-coding-guidelines.html Element sect1 in namespace '' encountered in article, but no template matches. Element title in namespace '' encountered in sect1, but no template matches. Element para in namespace '' encountered in sect1, but no template matches. Element para in namespace '' encountered in sect1, but no template matches. Element para in namespace '' encountered in sect1, but no template matches. Element emphasis in namespace '' encountered in para, but no template matches. Element para in namespace '' encountered in sect1, but no template matches. Element para in namespace '' encountered in sect1, but no template matches. Element sect1 in namespace '' encountered in article, but no template matches. Element title in namespace '' encountered in sect1, but no template matches. Element para in namespace '' encountered in sect1, but no template matches. Element filename in namespace '' encountered in para, but no template matches. …this continues for many lines… Instead, when I add xmlns:xsi='http://www.w3.org/2001/XMLSchema-instance' xsi:schemaLocation='http://docbook.org/ns/docbook [3] http://docbook.org/xml/5.0/xsd/docbook.xsd [4]' as attributes to article, and then also add the attributes to the independent documents, and also clean up a number of validation errors, both the mvn compile and separate xsltproc work without errors. (I'm not absolutely sure that you need to add all those attributes to the independent documents that get Xinclude'd, but I'm editing and validating with Eclipse, and it seems to need the schema for each document.) Hope it helps. Regards, Mark On Dec 2, 2011, at 12:04 PM, Giuseppe Greco wrote:Hi bob, Yes... I've a customization layer (http://www.agamura.com/docbook/stylesheets/current/ [1])... but this is not the problem since I get exactly the same result with the official docbook stylesheet. I've also tried to run docbkx in debug mode... but everything just looks fine (no errors, no warnings), and it doesn't matter whether or not I'm chunking HTML. If you want to give a look at my docbook source files, they are available for download here: https://github.com/agamura/home/tree/master/technotes [2] Thanks, j3d On 01.12.2011 19:10, Bob Stayton wrote:Hi Giuseppe,That red output indicates that the elements in the DocBook sourcefized by the stylesheet. In this case, it isrobably a mismatch in namwhen XIncluding DocBook 4 conocBook 5 book. Not sure why it only showse type="cite">up in HTML and not FO.ote>Does docbkx give you accessages? If so,ckquote type="cite">that will tell you more aboutlemeckquote>e type="cite">Are you using a stylesheet customization layer? Are yoblockquote> f the HTML output? lockquoteSagehill Enterprises gehill.net="cite">----- Original Message ----- FroGreco" ckqu te type="cite">To: &len.org>blockquote type="citeer 01, 2011 3:58 PMblockquote type="cite">SubHTML output...ockquote type="cite"> type /blockquote> ="ci blockquote> e">type="cite"> e completed my porting to docbook 5 an eworked my te type="cite">building system - I use docbk ugin that let me easickquote>nerate Huote>="cite"> "cit is perfect... while HTML output isn't. Here below is thequottype="cite"> L lockquote type="cite"kquote>e type="cite"> --------------------------------------------------------C# Coding Guidelinesype="cite">Giuseppe Greco e.greco@agamura.com>ockquote type="cite">3.0 uote type="cite"> te>Copyrigckquote type="cite"> ote>Al rved. This document is provided as-is and its content quote type="cite"> ckquote>Trademarks. Agamura and the Agamura logo are trademarkquote>type="cite">Inc. All other names are trademarks of their respective="cite"> e="cite"> cite"> "> e>________________________________________________ite"> Introduction document describes a te type="cite">set uote type="cite">of coding style guides f programs in the C# language. pe="cite"> A st a set offor layout and formatting. Uniforit easier for other uote type="cite">dev asp the essence of your programs quickly. uote type="cite">Aakes you more productive becauseces gratuitous choiceIf you do not have to make choices t quote type="cite">trivial matters, you can spend your energy on the solution of real te type="cite">problems. In these guidelines, several co r> ote> "cite">plainly outlawed... blockquote type="cite"> blockquote type="cite">--------------------------------------------------------------------------------ite"> e="cite">As you can see, title, legal notice, version are OK...while theblockquote>Switz/blockquote>type="cite">call giuseppe.greco via Skypephone: +41 (0)91 234 51 09te>mobile: +41 (0)79 590 33 06 pe="cite">email: giuseppe.greco@agamura.com"cite">----------------ite"> te">------------------------------------------------------------------ockquote>Toe-mail: docbook-unsubscribe@lists.oasis-open.orgdditional commands, e-mail: docbook-help@lists.oasis-open.org blockquote>Links: ------ [1] http://www.agamura.com/docbook/stylesheets/current/ [2] https://github.com/agamura/home/tree/master/technotes [3] http://docbook.org/ns/docbook [4] http://docbook.org/xml/5.0/xsd/docbook.xsd
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]