Re: Show chapters in both book and part TOCs

Hi Joel,
This turns out to be a bug in the stylesheets, for both fo and html.  I just fixed it 
in the SVN repository, so the changes should be in the next release.  The files I 
changed were fo/autotoc.xsl and html/autotoc.xsl if you want to pick them up from the 
SourceForge SVN repository and compare to your current version in case you need to fix 
this right away.

Thanks for the report.

Bob Stayton
Sagehill Enterprises
bobs <at> sagehill.net

----- Original Message ----- 
From: "Parker, Joel J. K. (GSFC-5950)" <joel.j.k.parker <at> nasa.gov>
To: "Bob Stayton" <bobs <at> sagehill.net>; <docbook-apps <at> lists.oasis-open.org>
Sent: Monday, October 31, 2011 10:26 AM
Subject: RE: [docbook-apps] Show chapters in both book and part TOCs

FO. I haven't tried HTML yet, but I can do that and let you know if it's the same.

- Joel

-----Original Message-----
From: Bob Stayton [mailto:bobs <at> sagehill.net]
Sent: Saturday, October 29, 2011 12:31 AM
To: Parker, Joel J. K. (GSFC-5950); docbook-apps <at> lists.oasis-open.org
Subject: Re: [docbook-apps] Show chapters in both book and part TOCs

Is this for FO output or HTML output?

RE: Generated epub to mobi - lists are incorrectly displayed

Re: [EPub] namespace problems

On 31.10.2011 17:34, Eric Johnson wrote:
> I'm using the Epub2 stylesheets. It turns out that the issue was in
> the titlepage customization that I was using. The titlepage.xsl
> generated from the template/titlepage.xsl didn't inlcude the xhtml
> namespace.
> 
> Once I manually added the namespace to the titlepage.xsl it worked fine.

Please note that I have recently updated template/titlepage.xsl that
generates titlepage templates to overcome this issue. However you have
to specify target namespace by using ns parameter, e.g.

saxon -o my-titlepage.xsl my-titlepage.xml .../template/titlepage.xsl
ns=http://www.w3.org/1999/xhtml

This should appear in the next release, but you can download just new
template/titlepage.xsl  from SVN if you don't want manually touch
generated titlepage files afrter each change.

				Jirka

--

-- 
------------------------------------------------------------------
  Jirka Kosek      e-mail: jirka <at> kosek.cz      http://xmlguru.cz
------------------------------------------------------------------
       Professional XML consulting and training services
  DocBook customization, custom XSLT/XSL-FO document processing
------------------------------------------------------------------
 OASIS DocBook TC member, W3C Invited Expert, ISO JTC1/SC34 member
------------------------------------------------------------------

Re: Generated epub to mobi - lists are incorrectly displayed

On 29.10.2011 11:59, Lars Vogel wrote:

> thanks. This also looks like a great solution. I think the suggestion from
> Robert is easier for my toolchain as I only have to change the customization
> layer and not have an additional step. But your suggestion is great as it
> shows options how to further influence the result.
> 
> How to you separate the step XHTML and EPUB creation? I believe the epub
> XSLT stylesheets do this in one step?

I use Ant to manage build process. I have separate target for Kindle
which applies this fixing transformation on output of DocBook
stylesheets before ziping final epub file. Something like:

  <target name="kindle">
    ... call normal DocBook epub stylesheet ..

    <!-- Make fixes for Kindle in generated XHTML -->
    <xslt style="kindleize.xsl" force="true" basedir="${out.dir}"
includes="*.xhtml" destdir="${out.dir}/kindle">
      <factory name="net.sf.saxon.TransformerFactoryImpl"/>
      <classpath location="${saxon9.jar}"/>
    </xslt>

    <!-- Replace original XHTML files with "kindleized" ones -->
    <copy todir="${out.dir}">
      <fileset dir="${out.dir}/kindle"/>
      <globmapper from="*.html" to="*.xhtml"/>
    </copy>

    <!-- Delete temporary "kindleized" files -->
    <delete dir="${out.dir}/kindle"/>

    <!-- Build final epub package -->
    <zip destfile="${out}-kindle.epub"
	 basedir="ebook"
	 includes="mimetype"
	 compress="false"
	 />
    <zip destfile="${out}-kindle.epub"
	 basedir="ebook"
	 excludes="mimetype"
	 update="true"
	 compress="true"
	 keepcompression="true"
	 />

  </target>

--

-- 
------------------------------------------------------------------
  Jirka Kosek     e-mail: jirka <at> kosek.cz     http://www.kosek.cz
------------------------------------------------------------------
  Profesionální školení a poradenství v oblasti technologií XML.
       Podrobný přehled školení http://xmlguru.cz/skoleni/
------------------------------------------------------------------
  http://docbook.cz    Stránky o dokumentačním formátu DocBook
  http://xmlguru.cz    Blog mostly about XML for English readers
------------------------------------------------------------------

Re: Generated epub to mobi - lists are incorrectly displayed

Indeed, and what if you want to have a list item with more than one
para as a child? I guess Kindle demands:

<li>This is my first para. <p>This is my second para.</p></li>

But then what if I want to add a class to that first <p> but not to
the second? I guess you'd have to wrap the first para in a div instead.

David

On 10/31/2011 11:16 PM, rob.cavicchio <at> emc.com wrote:
> I disagree. Under what circumstances do you think that anyone would
> want a bullet on a line by itself?
> 
> 
> *From:*Lars Vogel [mailto:lars.vogel <at> googlemail.com] *Sent:*
> Saturday, October 29, 2011 03:02 *To:* Jon Rosen *Cc:* Jirka Kosek;
> DocBook Apps *Subject:* Re: [docbook-apps] Generated epub to mobi -
> lists are incorrectly displayed
> 
> 
> 
> Hi Jon,
> 
> 
> 
> I think the browsers may have accepted that people do this and try
> to give a good display. I think Kindle acctually shows it correct.
> The instruction <li> <p> Text </p> </li> basically says: first make
> a list item then a paragraph and then the text.
> 
> 
> 
> Best regards, Lars
> 
> 2011/10/29 Jon Rosen <jon.rosen <at> ucirrus.com
> <mailto:jon.rosen <at> ucirrus.com>>
> 
> To be clear though, this is a problem with the mobi browser
> rendering of list items that are wrapped in <p> tags, not docbook.
> 
> The rendering of a <p> inside an <li> should NOT put the dot on a 
> separate line.  I tested this in Firefox and IE.  The <p> tag adds
> some spacing above and below the line, but the dot remains on the
> first paragraph line.
> 
> Jon Rosen
> 
> 
> -----Original Message----- From: Jirka Kosek [mailto:jirka <at> kosek.cz
> <mailto:jirka <at> kosek.cz>] Sent: Friday, October 28, 2011 3:28 PM To:
> Lars Vogel Cc: DocBook Apps Subject: Re: [docbook-apps] Generated
> epub to mobi - lists are incorrectly displayed
> 
> On 28.10.2011 16:38, Lars Vogel wrote:
> 
>> I'm generating epubs via Docbook and the epub XSLT stylesheets.
>> If I convert them to mobipocket for the Kindle lists are
>> incorrectly displayed.
>> 
>> <ul><li> Hello </li> </ul>
>> 
>> The dot is in one line and the text in another. Screenshot
>> attached.
>> 
>> I tried kindlegen and Calibre.
>> 
>> Anyone know how to solve this?
> 
> The problem is that DocBook stylesheets wrap content of listitem in
> <p> (because originaly it was <para> in DocBook). The easiest way
> how to fix this is to postprocess generated XHTML files and remove
> <p>s inside <li>. I'm using attached XSLT transformation (inspired
> by code provided by Adam Witwer originaly).
> 
> Jirka
> 
> -- 
> ------------------------------------------------------------------ 
> Jirka Kosek      e-mail: jirka <at> kosek.cz <mailto:jirka <at> kosek.cz>
>  http://xmlguru.cz 
> ------------------------------------------------------------------ 
> Professional XML consulting and training services DocBook
> customization, custom XSLT/XSL-FO document processing 
> ------------------------------------------------------------------ 
> OASIS DocBook TC member, W3C Invited Expert, ISO JTC1/SC34 member 
> ------------------------------------------------------------------
> 
> 
> 
> 
> 
> -- Lars http://www.vogella.de - Eclipse, Android and Java
> Tutorials http://www.twitter.com/vogella - Lars on Twitter
> 

Re: PDF toc (bookmark) depth

Bob,

Thanks. I guess I'll dive into the XSL. If I come up with something useful, I'll share it with the group.

Best Regards,
Dick
On Oct 31, 2011, at 4:54 PM, Bob Stayton wrote:

> Hi Dick,
> Right, there is no parameter that controls the depth of section levels in bookmarks. I have done it before
by customizing the templates that generate the bookmarks.
> 
> Bob Stayton
> Sagehill Enterprises
> bobs <at> sagehill.net
> 
> 
> ----- Original Message ----- From: "Richard Hamilton" <hamilton <at> xmlpress.net>
> To: "DocBook Apps" <docbook-apps <at> lists.oasis-open.org>
> Sent: Friday, October 28, 2011 10:05 PM
> Subject: [docbook-apps] PDF toc (bookmark) depth
> 
> 
> Is there an easy way (like a parameter:) to limit the depth of the PDF bookmarks generated by the fo stylesheets?
> 
> Right now, it looks like bookmarks are generated at all section levels, regardless of how deep the "real"
toc is set for. I'd like to limit them to match the toc level.
> 
> Looking at the mailing list archive and Bob's book, I don't see anything about this topic, but I figured I'd
ask on the list before diving into the code:).
> 
> If it makes a difference, I'm using the 1.76.1ns version of the stylesheets with XEP.
> 
> Thanks,
> Dick Hamilton
> -------
> XML Press
> XML for Technical Communicators
> http://xmlpress.net
> hamilton <at> xmlpress.net
> 
> 
> 
> 
> ---------------------------------------------------------------------
> 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
> 
> 
> 

Re: rotate figures with a pi

RE: Generated epub to mobi - lists are incorrectly displayed

Re: Generated epub to mobi - lists are incorrectly displayed

RE: syntax highlighting with xslt2/pygments/jython/saxon

|  -----Original Message-----
|  From: Andreas Reuleaux

|  java \
|  -cp 
|
"/opt/saxonhe/saxon9he.jar:/opt/dbk/xslt2/lib/docbook-xsl2-saxon.jar:/usr/sh
are/java/jython.jar" net.sf.saxon.Transform \
|  -init:docbook.Initializer \
|  -s:myfile.dbk \
|  -xsl:fo-xslt2.xsl \
|  -o:myfile.fo \
|  -xi:on \
|  -ext:on \
|  use.extensions=1 \
|  fop1.extensions=1
|   
|    OK, my toolchain still works, but no highlighting yet

At present, highlighting does not work for XSL-FO. There are two reasons as
far as I can tell:
1. The code for calling Pygments via Jython only handles (X)HTML output. 
2. Pygments does not provide an XSL-FO formatter.

For XHTML, it took me a while to figure out how to make highlighting work
(Saxon HE on Windows XP). These points were particularly important:

1. Add role="pygments" to the <programlisting> element in the source XML.

2. Add 

 -Dpython.path=<path to Pygments install dir>

to the "java" command. This was necessary in order to avoid "ImportError: No
module named pygments".

3. Add the output generated from this snippet,

 from pygments.formatters import HtmlFormatter
 print HtmlFormatter().get_style_defs()

to a CSS file, and ensure that this file is referenced in the output (see
the docbook.css parameter).

Below is the contents of my Windows BAT file. I run it from the root
directory of the 2.0.2 relase downloaded from http://docbook.github.com/.

----------
java
-Dpython.path=c:/Java/jython2.5.2/Lib/site-packages/Pygments-1.4-py2.5.egg ^
    -cp
c:/Java/saxon93/saxon9he.jar;./lib/docbook-xsl2-saxon.jar;c:/Java/jython2.5.
2/jython.jar ^
    net.sf.saxon.Transform ^
    -init:docbook.Initializer ^
    -s:verbatim.xml ^
    -xsl:./xslt/base/html/docbook.xsl ^
    -o:verbatim.html ^
    -xi:on ^
    -ext:on ^
    docbook.css=mydefault.css
----------

|  * Also there is mention of some python.path setting in ~/.jython 
|    what does that look exactely (the path to the script maybe)?

As an alternative to '-Dpython.path=...' at the command line, you can add 

 python.path=<path to Pygments install dir>

to ~/.jython.

See http://wiki.python.org/jython/UserGuide#the-jython-registry

 
|  * I use neither Saxon PE or EE, but saxonb and/or saxonhe
|    so I guess I don't have to set 
|  
|     <resources>
|      
|  <extensionFunction>org.docbook.extensions.xslt20.Cwd</extensi
onFunction>
|      
|  <extensionFunction>org.docbook.extensions.xslt20.ImageIntrins
ics</extensionFunction>
|      
|  <extensionFunction>org.docbook.extensions.xslt20.Pygmenter</e
xtensionFunction>
|    </resources>

That's right, configuration files cannot be used with Saxon HE. See
http://www.saxonica.com/documentation/configuration/configuration-file.xml.

Mauritz