DeanNelson | 1 Oct 01:09 2011
Picon

Re: Image location

Lars,
 
Setting the "image.src.path" parameter would eliminate a need to prefix the path on all images. However, that doesn't seem to be your problem. Everything you stated/done should be working. The FO code looks right and it does seem to fit the file structure.
 
I am assuming that you are under a Linux/Unix OS. That said, I would look at the upper/lower case filenames located in your images directory and make sure they correspond with how you called them in the XML code.. My users are Windows and Linux and we constantly run in to case issues that show up under Linux but not Windows.
 
As you can tell, we are now "reaching" a bit for the solution for you. Maybe the exact error from FOP would help?
 
Regards,
Dean Nelson
 
In a message dated 9/30/2011 3:31:58 P.M. Pacific Daylight Time, markus.hoenicka <at> mhoenicka.de writes:
Hi,

my directory setup is usually as follows (somewhat simplified):

~/mydoc/mydoc.xml
~/mydoc/Makefile
~/mydoc/images/myimage.png

mydoc.xml then uses relative paths to specify the image:

<imagedata align="center" scale="50" format="PNG"
            fileref="images/myimage.png"/>

Makefile is set up to invoke xsltproc and fop as needed. In order to 
transform this document, I cd to ~/mydoc and run make pdf. That's 
about it.

regards,
Markus

Quoting Lars Vogel <lars.vogel <at> googlemail.com>:

> Hi Chris,
>
> thanks for the answer unfortunately this also does not work.
>
> In which directory should the image be?
>
> Best regards, Lars
>
> 2011/9/30 Køi¹tof ®elechovski <giecrilj <at> stegny.2a.pl>
>
>> Dnia pi±tek, 30 wrze¶nia 2011 o 12:29:29 Lars Vogel napisa³(a):
>> > Hello,
>> >
>> > I'm trying to create PDF from my Docbook output via the corresponding
>> > stylesheets but FOP cannot find the image. I read Bobs description and I
>> > believe the path of the image is correctly setup.
>> >
>> > http://www.sagehill.net/docbookxsl/GraphicsLocations.html
>> > http://www.sagehill.net/docbookxsl/ModularDoc.html#XIncludeGraphics
>> >
>> > The generated FO source look like the following:
>> >
>> > <fo:block id="d0e101"><fo:external-graphic
>> > src="url(content/images/DojoFolder10.gif)" width="auto" height="auto"
>> > content-width="auto" content-height="auto"/></fo:block>
>>
>> That looks like relative path.
>>
>> >
>> > and files are in the following structure:
>> >
>> > article.fo
>> > /content/images/DojoFolder10.gif
>> >
>>
>> Did you try setting src="url(/content/images/DojoFolder10.gif)"?
>>
>> Chris
>> >
>>
>
>
>
> --
> Lars
> http://www.vogella.de - Eclipse, Android and Java Tutorials
> http://www.twitter.com/vogella - Lars on Twitter


--
Markus Hoenicka
http://www.mhoenicka.de
AQ score 38



---------------------------------------------------------------------
To unsubscribe, e-mail: docbook-apps-unsubscribe <at> lists.oasis-open.org
For additional commands, e-mail: docbook-apps-help <at> lists.oasis-open.org
Robert Nagle | 1 Oct 10:34 2011
Picon

re: Subject: DocBook epub3 beta 3 stylesheets available

Hi, there, thanks  for doing this and I appreciate the thoroughness of
the readme file.

One question. you said, "This directory contains a beta version of XSL
stylesheets for generating EPUB3 output from DocBook 4 content. The
stylesheets should work for DocBook5 content by first stripping off
the namespace, but that feature has not yet been extensively tested."

So if for my current project I use vanilla docbook 5 XSL (no
namespaces), it should work for me?

Robert

*************************

    From: "Bob Stayton" <bobs <at> sagehill.net>
    To: "DocBook Apps" <docbook-apps <at> lists.oasis-open.org>
    Date: Fri, 30 Sep 2011 04:34:00 -0700

Hi,

I have updated a beta 3 version of the epub3 stylesheets for DocBook
XSL to SourceForge. It is in this directory:

https://sourceforge.net/projects/docbook/files/epub3/

and the README there describes the changes to this version.

Bob Stayton
Sagehill Enterprises
bobs <at> sagehill.net

--

-- 
Robert Nagle
6121 Winsome Ln #56C, Houston TX 77057-5581
(H) 713 893 3424/ (W) 832-251-7522 Carbon Neutral Since Jan 2010
http://www.robertnagle.info
Bob Stayton | 1 Oct 11:48 2011
Picon

Re: re: Subject: DocBook epub3 beta 3 stylesheets available

> So if for my current project I use vanilla docbook 5 XSL (no
> namespaces), it should work for me?

Not sure what you mean here.  I consider "DocBook 5 XSL" to be the namespaced -ns- 
version of the stylesheets, because the -ns- version directly processes DocBook 5 
documents in the Docbook namespace.  The epub3 beta is written as an addon for the 
non-namespaced version of the stylesheet.  That version handles DocBook 4 documents 
directly, and it handles DocBook 5 documents by first stripping off the namespace of 
the document elements and then processing it as a Docbook 4 document.

If you install the addon with the -ns- namespaced stylesheets, I don't think it will 
work for either DocBook  4 or 5.  If you install it with the non-namespaced 
stylesheets, then it should work with either DocBook 4 or 5.  It has been tested by me 
with only one Docbook 5 document so far.  Does that answer your question?

If you are asking if the
Bob Stayton
Sagehill Enterprises
bobs <at> sagehill.net

----- Original Message ----- 
From: "Robert Nagle" <idiotprogrammer <at> gmail.com>
To: "Bob Stayton" <bobs <at> sagehill.net>; <docbook-apps <at> lists.oasis-open.org>
Sent: Saturday, October 01, 2011 1:34 AM
Subject: [docbook-apps] re: Subject: DocBook epub3 beta 3 stylesheets available

> Hi, there, thanks  for doing this and I appreciate the thoroughness of
> the readme file.
>
> One question. you said, "This directory contains a beta version of XSL
> stylesheets for generating EPUB3 output from DocBook 4 content. The
> stylesheets should work for DocBook5 content by first stripping off
> the namespace, but that feature has not yet been extensively tested."
>
> So if for my current project I use vanilla docbook 5 XSL (no
> namespaces), it should work for me?
>
> Robert
>
> *************************
>
>
>    From: "Bob Stayton" <bobs <at> sagehill.net>
>    To: "DocBook Apps" <docbook-apps <at> lists.oasis-open.org>
>    Date: Fri, 30 Sep 2011 04:34:00 -0700
>
> Hi,
>
> I have updated a beta 3 version of the epub3 stylesheets for DocBook
> XSL to SourceForge. It is in this directory:
>
> https://sourceforge.net/projects/docbook/files/epub3/
>
> and the README there describes the changes to this version.
>
> Bob Stayton
> Sagehill Enterprises
> bobs <at> sagehill.net
>
>
>
>
> -- 
> Robert Nagle
> 6121 Winsome Ln #56C, Houston TX 77057-5581
> (H) 713 893 3424/ (W) 832-251-7522 Carbon Neutral Since Jan 2010
> http://www.robertnagle.info
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: docbook-apps-unsubscribe <at> lists.oasis-open.org
> For additional commands, e-mail: docbook-apps-help <at> lists.oasis-open.org
>
>
> 
Lars Vogel | 1 Oct 12:33 2011

Re: Image location

Hello Markus and Dean,


thanks for your replies. Based on your feedback I was able to find my issue. It seems that the path is relative to the Apache Ant build.xml I'm using and to the .fo file which is processed by the build.xml file.

If I put the graphics relativ to the build.xml (which I keep separated from the content) everything works.

The Ant File I'm currently using is:

---------------
<target name="build-pdf" depends="clean, copybookimage,  xinclude" description="Generates pdf files from DocBook XML">
<!-- Convert DocBook Files into FO -->
<xslt style="${fo.stylesheet}" extension=".fo" basedir="${outputtmp.dir}" destdir="${fobtmp.dir}">
<include name="**/*/article.xml" />
<param name="section.autolabel" expression="1" />
<param name="page.margin.inner" expression="1cm" />
<param name="page.margin.outer" expression="1cm" />
<param name="body.start.indent" expression="0mm" />
<param name="double-sided" expression="1" />
<param name="paper.type" expression="A4" />
</xslt>
<!-- Convert FO Files into pdf -->
<fop format="application/pdf" outdir="${pdf.dir}">
<fileset dir="${fobtmp.dir}">
<include name="**/*.fo" />
</fileset>
</fop>
</target>
--------------

Is there a way to tell the fop Ant Task to use a path relativ to the .fo file is processes? 

Best regards, Lars


2011/10/1 <DeanNelson <at> aol.com>
Lars,
 
Setting the "image.src.path" parameter would eliminate a need to prefix the path on all images. However, that doesn't seem to be your problem. Everything you stated/done should be working. The FO code looks right and it does seem to fit the file structure.
 
I am assuming that you are under a Linux/Unix OS. That said, I would look at the upper/lower case filenames located in your images directory and make sure they correspond with how you called them in the XML code.. My users are Windows and Linux and we constantly run in to case issues that show up under Linux but not Windows.
 
As you can tell, we are now "reaching" a bit for the solution for you. Maybe the exact error from FOP would help?
 
Regards,
Dean Nelson
 
In a message dated 9/30/2011 3:31:58 P.M. Pacific Daylight Time, markus.hoenicka <at> mhoenicka.de writes:
Hi,

my directory setup is usually as follows (somewhat simplified):

~/mydoc/mydoc.xml
~/mydoc/Makefile
~/mydoc/images/myimage.png

mydoc.xml then uses relative paths to specify the image:

<imagedata align="center" scale="50" format="PNG"
            fileref="images/myimage.png"/>

Makefile is set up to invoke xsltproc and fop as needed. In order to 
transform this document, I cd to ~/mydoc and run make pdf. That's 
about it.

regards,
Markus

Quoting Lars Vogel <lars.vogel <at> googlemail.com>:

> Hi Chris,
>
> thanks for the answer unfortunately this also does not work.
>
> In which directory should the image be?
>
> Best regards, Lars
>
> 2011/9/30 Køi¹tof ®elechovski <giecrilj <at> stegny.2a.pl>
>
>> Dnia pi±tek, 30 wrze¶nia 2011 o 12:29:29 Lars Vogel napisa³(a):

>> > Hello,
>> >
>> > I'm trying to create PDF from my Docbook output via the corresponding
>> > stylesheets but FOP cannot find the image. I read Bobs description and I
>> > believe the path of the image is correctly setup.
>> >
>> > http://www.sagehill.net/docbookxsl/GraphicsLocations.html
>> > http://www.sagehill.net/docbookxsl/ModularDoc.html#XIncludeGraphics
>> >
>> > The generated FO source look like the following:
>> >
>> > <fo:block id="d0e101"><fo:external-graphic
>> > src="url(content/images/DojoFolder10.gif)" width="auto" height="auto"
>> > content-width="auto" content-height="auto"/></fo:block>
>>
>> That looks like relative path.
>>
>> >
>> > and files are in the following structure:
>> >
>> > article.fo
>> > /content/images/DojoFolder10.gif
>> >
>>
>> Did you try setting src="url(/content/images/DojoFolder10.gif)"?
>>
>> Chris
>> >
>>
>
>
>
> --
> Lars
> http://www.vogella.de - Eclipse, Android and Java Tutorials
> http://www.twitter.com/vogella - Lars on Twitter


--
Markus Hoenicka
http://www.mhoenicka.de
AQ score 38



---------------------------------------------------------------------
To unsubscribe, e-mail: docbook-apps-unsubscribe <at> lists.oasis-open.org
For additional commands, e-mail: docbook-apps-help <at> lists.oasis-open.org



--
Lars
http://www.vogella.de - Eclipse, Android and Java Tutorials
http://www.twitter.com/vogella - Lars on Twitter
Tom Browder | 1 Oct 16:56 2011
Picon

Re: Image location

On Sat, Oct 1, 2011 at 05:33, Lars Vogel <lars.vogel <at> googlemail.com> wrote:
...
> If I put the graphics relativ to the build.xml (which I keep separated from
> the content) everything works.
> The Ant File I'm currently using is:
> ---------------
> <target name="build-pdf" depends="clean, copybookimage,  xinclude"
> description="Generates pdf files from DocBook XML">
> <!-- Convert DocBook Files into FO -->
> <xslt style="${fo.stylesheet}" extension=".fo" basedir="${outputtmp.dir}"
> destdir="${fobtmp.dir}">
> <include name="**/*/article.xml" />
> <param name="section.autolabel" expression="1" />
> <param name="page.margin.inner" expression="1cm" />
> <param name="page.margin.outer" expression="1cm" />
> <param name="body.start.indent" expression="0mm" />
> <param name="double-sided" expression="1" />
> <param name="paper.type" expression="A4" />
> </xslt>
> <!-- Convert FO Files into pdf -->
> <fop format="application/pdf" outdir="${pdf.dir}">
> <fileset dir="${fobtmp.dir}">
> <include name="**/*.fo" />
> </fileset>
> </fop>
> </target>
> --------------
>
> Is there a way to tell the fop Ant Task to use a path relativ to the .fo
> file is processes?
> Best regards, Lars

Have you tried xml catalog with the prefix rewrite rule to generate
fo?  That has solved a lot of path problems for me.  Of course I'm
using xsltproc with which that is easy--don't know if an ant and
whatever tool chain will work.

Best,

-Tom
Bob Stayton | 1 Oct 20:34 2011
Picon

Re: Modifying line-height for table title

Hi Dave,
In order to make the titles of figures, tables, examples consistent in format, there is a separate attribute-set for them named 'formal.title.properties'.  See this reference for details:
 
 
jThat att-set does not actually set the line-height property, so I think the title is inheriting it from the root.properties attribute set, which sets its value to 'normal'.  Most FO processors interpret 'normal' as 1.2em. 
 
Bob Stayton
Sagehill Enterprises
bobs <at> sagehill.net
 
 
----- Original Message -----
Sent: Thursday, September 29, 2011 5:54 AM
Subject: [docbook-apps] Modifying line-height for table title

I have set a parameter for line-height (“graphiclineheight”= 1) that works for all text within formal objects - figure, example and the body of tables (i.e. text within table.table). This parameter though doesn’t modify the line-height for d:table/d:title. I looked at the FO output and it seems that d:table/d:title is picking up the line-height for body text, which is 1.2. I have experimented with adding a specific smaller line-height (0.8) within table.properties then the ‘graphiclineheight’ one within table.table.properties, but this only modifies the line height of footnotes which I know is modified by attributes within table.properties – but the table title inexplicably remains unchanged.
I’ve tried to find some relevant fo:block code within tables.xsl and formal.xsl, but I can’t see what else to modify.
Here are my customisations that incorporate line-height for tables:
 
In “tables.xsl”:
  <xsl:param name="tabletitlelineheight">0.8 </xsl:param>
  <xsl:attribute-set name="table.properties">
   
<xsl:attribute name="keep-together.within-column">auto </xsl:attribute> <!-- allows tables to
      break ('auto') or not break ('always') across pages -->
   
<xsl:attribute name="background-color"></xsl:attribute> <!-- specify
      web colour (e.g. #e0e0e0) *****works 28/9/11 -->
   
<xsl:attribute name="hyphenate"> false </xsl:attribute> <!--hyphenation of text;
      default: false (do not hyphenate). OPTIONS: false, true-->
   
<xsl:attribute name="text-align"> justify </xsl:attribute> <!--alignment of table
      title. OPTIONS: left, justify *****works 28/9/11-->
   
<xsl:attribute name="margin-left"> 0pt </xsl:attribute> <!--indent from left
      margin*****works 28/9/11-->
   
<xsl:attribute name="margin-right"> 0pt </xsl:attribute> <!--indent from right
      margin*****works 28/9/11-->
   
<xsl:attribute name="margin-top"> 0pt </xsl:attribute> <!--top margin*****-->
   
<xsl:attribute name="margin-bottom"> 10pt </xsl:attribute> <!--add leading
      after a table (including after footnotes), to adjust text on
      page*****works 28/9/11-->
   
<!--padding inside table region*****works 20/9/11-->
   
<xsl:attribute name="padding-left"> 0pt </xsl:attribute>
   
<xsl:attribute name="padding-right"> 0pt </xsl:attribute>
   
<xsl:attribute name="padding-top"> 0pt </xsl:attribute>
   
<xsl:attribute name="padding-bottom"> 0pt </xsl:attribute>
   
<xsl:attribute name="line-height">
     
<xsl:value-of select="$tabletitlelineheight"/>
   
</xsl:attribute>
 
</xsl:attribute-set>
<xsl:attribute-set name= "table.table.properties">
   
<xsl:attribute name="line-height">
     
<xsl:value-of select="$graphiclineheight"/>
   
</xsl:attribute>
   
<xsl:attribute name="background-color"> #e0e0e0 </xsl:attribute> <!-- specify web colour
      (e.g. #e0e0e0) *****-->   
   
<xsl:attribute name="font-size">
     
<xsl:choose>
       
<xsl:when test="ancestor-or-self::d:informaltable">
         
<xsl:value-of select="$body.font.master * 1"/> <xsl:text> pt </xsl:text>
         
<!-- informal tables have same font size as body text -->
       
</xsl:when>
       
<xsl:otherwise>
         
<xsl:value-of select="$body.font.master * 0.8"/> <xsl:text> pt </xsl:text> <!-- small font for all
            formal tables -->  
       
</xsl:otherwise>
     
</xsl:choose>
   
</xsl:attribute>
   
<xsl:attribute name="text-align"> left </xsl:attribute>
   
   
<xsl:attribute name="border-after-width.conditionality">retain </xsl:attribute> <!-- displays
      bottom border for a table that breaks across to the next page; options: discard [default], retain -->
   
<xsl:attribute name="border-before-width.conditionality">retain </xsl:attribute> <!-- displays
      top border for a table that breaks across from the previous page; options: discard [default], retain -->
   
<xsl:attribute name="hyphenate"> false </xsl:attribute> <!-- hyphenation in
      tables; 'true' means turn on hyphenation -->
   
<xsl:attribute name="border-collapse"> collapse </xsl:attribute> <!-- merge borders
      together for adjacent cells -->
 
</xsl:attribute-set>
 
And in “graphics.xsl”:
  <xsl:param name="graphiclineheight">
   
<xsl:choose>
     
<xsl:when test = "$graphicfontstyle='sans-serif'">
        
<xsl:value-of select="$line-height * 1"/>
     
</xsl:when>
     
<xsl:otherwise>
       
<xsl:value-of select="$line-height"/>
     
</xsl:otherwise>
   
</xsl:choose>
 
</xsl:param>
 
See attached for sample FO output.
Thanks,
 
Dave Gardiner


---------------------------------------------------------------------
To unsubscribe, e-mail: docbook-apps-unsubscribe <at> lists.oasis-open.org
For additional commands, e-mail: docbook-apps-help <at> lists.oasis-open.org
Lars Vogel | 1 Oct 20:38 2011

Re: Image location

Hi Tom,


I would prefer if the path could just be relative to the .fo file. Introducing a xml catalog and a new re-write rule seems unnecessary complex. 

I could fix it within my ant tasks copying the images into the build project but this doesn't not seem like a solid solution to me. 

Best regards, Lars

2011/10/1 Tom Browder <tom.browder <at> gmail.com>
On Sat, Oct 1, 2011 at 05:33, Lars Vogel <lars.vogel <at> googlemail.com> wrote:
...
> If I put the graphics relativ to the build.xml (which I keep separated from
> the content) everything works.
> The Ant File I'm currently using is:
> ---------------
> <target name="build-pdf" depends="clean, copybookimage,  xinclude"
> description="Generates pdf files from DocBook XML">
> <!-- Convert DocBook Files into FO -->
> <xslt style="${fo.stylesheet}" extension=".fo" basedir="${outputtmp.dir}"
> destdir="${fobtmp.dir}">
> <include name="**/*/article.xml" />
> <param name="section.autolabel" expression="1" />
> <param name="page.margin.inner" expression="1cm" />
> <param name="page.margin.outer" expression="1cm" />
> <param name="body.start.indent" expression="0mm" />
> <param name="double-sided" expression="1" />
> <param name="paper.type" expression="A4" />
> </xslt>
> <!-- Convert FO Files into pdf -->
> <fop format="application/pdf" outdir="${pdf.dir}">
> <fileset dir="${fobtmp.dir}">
> <include name="**/*.fo" />
> </fileset>
> </fop>
> </target>
> --------------
>
> Is there a way to tell the fop Ant Task to use a path relativ to the .fo
> file is processes?
> Best regards, Lars

Have you tried xml catalog with the prefix rewrite rule to generate
fo?  That has solved a lot of path problems for me.  Of course I'm
using xsltproc with which that is easy--don't know if an ant and
whatever tool chain will work.

Best,

-Tom

---------------------------------------------------------------------
To unsubscribe, e-mail: docbook-apps-unsubscribe <at> lists.oasis-open.org
For additional commands, e-mail: docbook-apps-help <at> lists.oasis-open.org




--
Lars
http://www.vogella.de - Eclipse, Android and Java Tutorials
http://www.twitter.com/vogella - Lars on Twitter
Larry Garfield | 1 Oct 22:13 2011

HTML5 version?

Hi folks.  At the moment I'm using the XHTML version of the DocBook XSL 
scripts.  That's mostly fine, but I am trying to convert all of my web 
work over th HTML5.  (Vis, using more semantic tags, reduced-complexity 
head elements, fewer extra wrapping divs, assuming that CSS actually 
works now so I can use modern selectors for styling, etc.)  I saw that 
the EPUB target that Bob is working on (Go Bob!) is using HTML5 
internally, but is that available separately as its own target?  Just 
straight up HTML5 "thin" markup for web use?

--Larry Garfield
Lars Vogel | 1 Oct 22:56 2011

Re: Image location

Hello,


I found the parameter "keep.relative.image.uris" which reduces my complexity. This way I have to copy the images only to one location relatively to the build.xml. I would be still nicer if I could configure the FOP task to use a  path relative to the .fo file but I assume this is not really a question for the docbook mailing list.

Thanks to everyone.

Best regards, Lars



2011/10/1 Lars Vogel <lars.vogel <at> googlemail.com>
Hi Tom,

I would prefer if the path could just be relative to the .fo file. Introducing a xml catalog and a new re-write rule seems unnecessary complex. 

I could fix it within my ant tasks copying the images into the build project but this doesn't not seem like a solid solution to me. 

Best regards, Lars


2011/10/1 Tom Browder <tom.browder <at> gmail.com>
On Sat, Oct 1, 2011 at 05:33, Lars Vogel <lars.vogel <at> googlemail.com> wrote:
...
> If I put the graphics relativ to the build.xml (which I keep separated from
> the content) everything works.
> The Ant File I'm currently using is:
> ---------------
> <target name="build-pdf" depends="clean, copybookimage,  xinclude"
> description="Generates pdf files from DocBook XML">
> <!-- Convert DocBook Files into FO -->
> <xslt style="${fo.stylesheet}" extension=".fo" basedir="${outputtmp.dir}"
> destdir="${fobtmp.dir}">
> <include name="**/*/article.xml" />
> <param name="section.autolabel" expression="1" />
> <param name="page.margin.inner" expression="1cm" />
> <param name="page.margin.outer" expression="1cm" />
> <param name="body.start.indent" expression="0mm" />
> <param name="double-sided" expression="1" />
> <param name="paper.type" expression="A4" />
> </xslt>
> <!-- Convert FO Files into pdf -->
> <fop format="application/pdf" outdir="${pdf.dir}">
> <fileset dir="${fobtmp.dir}">
> <include name="**/*.fo" />
> </fileset>
> </fop>
> </target>
> --------------
>
> Is there a way to tell the fop Ant Task to use a path relativ to the .fo
> file is processes?
> Best regards, Lars

Have you tried xml catalog with the prefix rewrite rule to generate
fo?  That has solved a lot of path problems for me.  Of course I'm
using xsltproc with which that is easy--don't know if an ant and
whatever tool chain will work.

Best,

-Tom

---------------------------------------------------------------------
To unsubscribe, e-mail: docbook-apps-unsubscribe <at> lists.oasis-open.org
For additional commands, e-mail: docbook-apps-help <at> lists.oasis-open.org



Bob Stayton | 2 Oct 00:02 2011
Picon

Re: HTML5 version?

Yes, HTML5 is available as a separate target for output, but it currently comes with a 
few caveats.

The epub3 add-on that I've posted has two directories: xhtml5 and epub3.  You should 
be able to use the stylesheets in the xhtml5 directory to produce HTML5 output with 
XML serialization.

The xhtml5 stylesheets are actually customization layers of the stylesheets in the 
xhtml directory.  That was the shortest path to getting HTML5 output while retaining 
the myriad features of DocBook's HTML collection of stylesheets. However, that 
approach is likely to compromise the "purity" of the HTML5 output until the 
customization layer is improved sufficiently to catch and correct all the impurities 
in the xhtml stylesheet.  It is not there yet.

If you have started working with HTML5, then you are probably aware that no DTD or 
schema exists for it, nor will it.  See this thread for further discussion:

http://stackoverflow.com/questions/4055206/yet-another-question-regarding-the-html5-dtd-schema

The intent of the HTML5 developers is to use dedicated HTML5 validator programs 
instead of general XML validators.  I have been using the W3C online validator for 
HTML5, and I have the beta xhtml5 stylesheets producing valid output for a subset of 
DocBook test documents. I have not tested the full complement of DocBook elements, and 
I have not tested many combinations of elements. I know there are untested DocBook 
elements that produce dirty HTML5, but I have not yet gotten to handling those yet 
with the customization layer. This is the primary reason why these stylesheets are 
still in beta.  They need further development and broader testing before being put 
into production systems.

My focus has been getting HTML5 output of sufficient quality to build epub3 documents. 
The Epub3 developers  *have* created an RNC schema for HTML5 (XML version), over which 
they have layered their schema for EPUB3.  So most of my daily testing is with these 
schemas, which do report errors in HTML5 elements, at least as interpreted by the 
creators of their unofficial HTML5 schemas. I have also been testing with epubcheck 
for EPUB3, which also reports problems with HTML5 elements.

So if you want to join the bleeding edge, be my guest, but be aware that you will 
probably run into problems for awhile.  I would of course  appreciate any bug reports.

Bob Stayton
Sagehill Enterprises
bobs <at> sagehill.net

----- Original Message ----- 
From: "Larry Garfield" <larry <at> garfieldtech.com>
To: <docbook-apps <at> lists.oasis-open.org>
Sent: Saturday, October 01, 2011 1:13 PM
Subject: [docbook-apps] HTML5 version?

> Hi folks.  At the moment I'm using the XHTML version of the DocBook XSL scripts. 
> That's mostly fine, but I am trying to convert all of my web work over th HTML5. 
> (Vis, using more semantic tags, reduced-complexity head elements, fewer extra 
> wrapping divs, assuming that CSS actually works now so I can use modern selectors 
> for styling, etc.)  I saw that the EPUB target that Bob is working on (Go Bob!) is 
> using HTML5 internally, but is that available separately as its own target?  Just 
> straight up HTML5 "thin" markup for web use?
>
> --Larry Garfield
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: docbook-apps-unsubscribe <at> lists.oasis-open.org
> For additional commands, e-mail: docbook-apps-help <at> lists.oasis-open.org
>
>
> 

Gmane