To see the stylesheet errors from sickbed messages, do "mvn -X" David -- Sent from my Android phone with K-9 Mail. Please excuse my brevity.
Bob Stayton <b...@sagehill.net> 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 b...@sagehill.net ----- Original Message ----- From: "Giuseppe Greco" <giuseppe.gr...@agamura.com> To: <docbook@lists.oasis-open.org> 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 > <giuseppe.gr...@agamura.com> > > > 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: giuseppe.gr...@agamura.com >_____________________________________________ > > >_____________________________________________ > To unsubscribe, e-mail: docbook-unsubscr...@lists.oasis-open.org > For additional commands, e-mail: docbook-h...@lists.oasis-open.org > > > _____________________________________________ To unsubscribe, e-mail: docbook-unsubscr...@lists.oasis-open.org For additional commands, e-mail: docbook-h...@lists.oasis-open.org
