... fixed :-) I just had to add
xmlns:xsi='http://www.w3.org/2001/XMLSchema-instance'
xsi:schemaLocation='http://docbook.org/ns/docbook
http://docbook.org/xml/5.0/xsd/docbook.xsd' to the first element of each
separate xml file.
Last question: the appendix is no longer autolabeled... so I added this
to my customization layer:
<xsl:param name="appendix.autolabel" select="1"/>
... but the appendix label is still missing. Is there something else I
need to be aware of?
tx,
j3d
On Fri, 2011-12-02 at 13:30 +0100, Mark Craig wrote:
> Hello,
>
>
> When I
> add <generatedSourceDirectory>${basedir}/generated</generatedSourceDirectory>
> 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
> http://docbook.org/xml/5.0/xsd/docbook.xsd'
> 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/)... 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
> >
> > Thanks,
> > j3d
> >
> > On 01.12.2011 19:10, Bob Stayton wrote:
> > > Hi Giuseppe,
> > > That red output indicates that the elements in the DocBook source
> > > file are not being recognized by the stylesheet. In this case, it
> > > is
> > > probably a mismatch in namespace. That can happen when XIncluding
> > > DocBook 4 content into a DocBook 5 book. Not sure why it only
> > > shows
> > > up in HTML and not FO.
> > >
> > > Does docbkx give you access to stylesheet error messages? If so,
> > > that will tell you more about the mismatch of these elements.
> > >
> > > Are you using a stylesheet customization layer? Are you doing
> > > chunking of the HTML output?
> > >
> > > Bob Stayton
> > > Sagehill Enterprises
> > > [email protected]
> > >
> > >
> > > ----- Original Message ----- From: "Giuseppe Greco"
> > > <[email protected]>
> > > To: <[email protected]>
> > > Sent: Thursday, December 01, 2011 3:58 PM
> > > Subject: [docbook] Strange HTML output...
> > >
> > >
> > > > Hi,
> > > >
> > > > I've completed my porting to docbook 5 and I've also reworked my
> > > > building system - I use docbkx, a maven plugin that let me
> > > > easily
> > > > generate HTML and PDF.
> > > >
> > > > PDF output is perfect... while HTML output isn't. Here below is
> > > > the
> > > > HTML
> > > > output I get:
> > > >
> > > >
> > > >
> > --------------------------------------------------------------------------------------
> > > > C# Coding Guidelines
> > > > Giuseppe Greco
> > > > <[email protected]>
> > > >
> > > >
> > > > 3.0
> > > >
> > > >
> > > > Copyright © 2012 Agamura, Inc.
> > > >
> > > >
> > > > All rights reserved. This document is provided as-is and its
> > > > content
> > > > may
> > > > change without prior notice - you bear the risk of using it. You
> > > > may
> > > > copy and use this document without limitation, but it does not
> > > > provide
> > > > you with any legal right to any intellectual property of
> > > > Agamura,
> > > > Inc.
> > > >
> > > > Trademarks. Agamura and the Agamura logo are trademarks of
> > > > Agamura,
> > > > Inc. All other names are trademarks of their respective owners.
> > > >
> > > >
> > > >
> > > >
> > ________________________________________________________________________
> > > > <sect1> <title>Introduction</title> <para> This document
> > > > describes a
> > > > set
> > > > of coding style guides for developing programs in the C#
> > > > language.
> > > > </para> <para> A style guide is a set of mandatory requirements
> > > > for
> > > > layout and formatting. Uniform style makes it easier for other
> > > > developers to grasp the essence of your programs quickly.
> > > > </para>
> > > > <para>
> > > > A style guide makes you more productive because it
> > > > <emphasis>reduces
> > > > gratuitous choice</emphasis>. If you do not have to make
> > > > choices
> > > > about
> > > > trivial matters, you can spend your energy on the solution of
> > > > real
> > > > problems. </para> <para> In these guidelines, several
> > > > constructors
> > > > are
> > > > plainly outlawed...
> > > >
> > > >
> > --------------------------------------------------------------------------------------
> > > >
> > > > As you can see, title, legal notice, version are OK... while
> > > > the
> > > > rest
> > > > (i.e. sect1) isn't. The docbook tags are output as they are in
> > > > the
> > > > source files - more or less, here is the real HTML code:
> > > >
> > > > ...
> > > > <span style="color: red"><para>
> > > > This document describes a set of coding style guides for
> > > > developing
> > > > programs in the C# language.
> > > > </para></span>
> > > > ...
> > > >
> > > > Does anybody already experienced something similar? Any help
> > > > would
> > > > be
> > > > reeeally appreciated.
> > > >
> > > > Thanks a lot,
> > > > j3d
> > > >
> > > > -- ----------------------------------------
> > > > Giuseppe Greco
> > > > 6949 Comano
> > > > Switzerland
> > > >
> > > > call giuseppe.greco via Skype
> > > > phone: +41 (0)91 234 51 09
> > > > mobile: +41 (0)79 590 33 06
> > > > email: [email protected]
> > > > ----------------------------------------
> > > >
> > > >
> > > >
> > > > ---------------------------------------------------------------------
> > > > To unsubscribe, e-mail: [email protected]
> > > > For additional commands, e-mail:
> > > > [email protected]
> > > >
> > > >
> > > >
> >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: [email protected]
> > For additional commands, e-mail: [email protected]
> >
> >
>
>
--
----------------------------------------
Giuseppe Greco
6949 Comano
Switzerland
call giuseppe.greco via Skype
phone: +41 (0)91 234 51 09
mobile: +41 (0)79 590 33 06
email: [email protected]
----------------------------------------
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
