docbook-apps

Hi, I browsed through the docbook.xsl file in the epub directory, and
I see some unfamiliar parameters.

Most I can guess the function of, but a few left me puzzled. Anyone
know what they refer to:

epub.cover.linear ?
ade.extensions ? (Adobe digital editions?)


Also, mobipocket requires a TOC in the main body but epub does not. if
I want to suppress the TOC in the main body (while leaving the ebook
reading software to construct it from the content.opf file) how would
I do this?

rj


******************************************
<xsl:param name="chunk.tocs.and.lots">1</xsl:param>
<xsl:param name="toc.section.depth">2</xsl:param>
<xsl:param name="generate.toc">
book toc,title
</xsl:param>
<xsl:param name="ade.extensions" select="0"/>
<xsl:param name="epub.autolabel" select="'1'"/>
<xsl:param name="epub.ncx.depth">4</xsl:param>
-

<xsl:param name="manifest.in.base.dir" select="'1'"/>
<xsl:param name="base.dir" select="$epub.oebps.dir"/>
<xsl:param name="epub.oebps.dir" select="'OEBPS/'"/>
<xsl:param name="epub.ncx.filename" select="'toc.ncx'"/>
<xsl:param name="epub.container.filename" select="'container.xml'"/>
<xsl:param name="epub.opf.filename" select="concat($epub.oebps.dir,
'content.opf')"/>
<xsl:param name="epub.cover.filename" select="concat($epub.oebps.dir,
'cover', $html.ext)"/>
<xsl:param name="epub.cover.id" select="'cover'"/>
<xsl:param name="epub.cover.html" select="'cover.html'"/>
<xsl:param name="epub.cover.image.id" select="'cover-image'"/>
<xsl:param name="epub.cover.linear" select="0"/>
<xsl:param name="epub.ncx.toc.id">ncxtoc</xsl:param>
<xsl:param name="epub.html.toc.id">htmltoc</xsl:param>
<xsl:param name="epub.metainf.dir" select="'META-INF/'"/>
<xsl:param name="epub.embedded.fonts"/>
-


--
Robert Nagle
12777 Ashford Point Dr #1417
Houston, Texas 77082
713 893 3424
http://www.robertnagle.info

On Wed, Dec 1, 2010 at 10:53 PM, Robert Nagle <idiotprogrammer@gmail.com> wrote:
> Hi, I browsed through the docbook.xsl file in the epub directory, and
> I see some unfamiliar parameters.

Yes, most of them are not actually intended for external customization.

> Most I can guess the function of, but a few left me puzzled. Anyone
> know what they refer to:
>
> epub.cover.linear ?

Some publishers prefer the cover (XHTML file) to be the first document
displayed to a reader, while others want the first "real" bit of
content. If epub.cover.linear is non-zero, the cover file will be
marked as the first file to open (in the linear reading order of the
OPF spine). More on the best practices around covers here:
http://blog.threepress.org/2009/11/20/best-practices-in-epub-cover-images/

> ade.extensions ? (Adobe digital editions?)

Yes, Adobe Digital Editions, but unused at this time.


> Also, mobipocket requires a TOC in the main body but epub does not. if
> I want to suppress the TOC in the main body (while leaving the ebook
> reading software to construct it from the content.opf file) how would
> I do this?

One technique for getting around this problem is described here:
http://blog.threepress.org/2010/11/16/better-single-source-mobiepub-files/
..that said, many folks generate a "real" EPUB and a highly degraded
one for Mobi conversion.

I've been studying the Mobipocket format (with Joshua Tallent's
excellent book on Kindle formatting).

Much of the limited styling available for it comes from HTML classes
of elements having to do with presentation. This doesn't seem to be
good semantics and frankly, doesn't seem very compatible with html
generated from docbook. It seems the only way to get an epub ready
for kindlegen is to do a lot of profiling..

Which reminds me: What's the easiest way in your customization layer
to suppress an single instance of a HTML element?


Robert

On Thu, Dec 2, 2010 at 1:10 AM, Keith Fahlgren <abdelazer@gmail.com> wrote:
> On Wed, Dec 1, 2010 at 10:53 PM, Robert Nagle <idiotprogrammer@gmail.com> wrote:
>> Hi, I browsed through the docbook.xsl file in the epub directory, and
>> I see some unfamiliar parameters.
>
> Yes, most of them are not actually intended for external customization.
>
>> Most I can guess the function of, but a few left me puzzled. Anyone
>> know what they refer to:
>>
>> epub.cover.linear ?
>
> Some publishers prefer the cover (XHTML file) to be the first document
> displayed to a reader, while others want the first "real" bit of
> content. If epub.cover.linear is non-zero, the cover file will be
> marked as the first file to open (in the linear reading order of the
> OPF spine). More on the best practices around covers here:
> http://blog.threepress.org/2009/11/20/best-practices-in-epub-cover-images/
>
>> ade.extensions ? (Adobe digital editions?)
>
> Yes, Adobe Digital Editions, but unused at this time.
>
>
>> Also, mobipocket requires a TOC in the main body but epub does not. if
>> I want to suppress the TOC in the main body (while leaving the ebook
>> reading software to construct it from the content.opf file) how would
>> I do this?
>
> One technique for getting around this problem is described here:
> http://blog.threepress.org/2010/11/16/better-single-source-mobiepub-files/
> ..that said, many folks generate a "real" EPUB and a highly degraded
> one for Mobi conversion.
>



--
Robert Nagle
12777 Ashford Point Dr #1417
Houston, Texas 77082
713 893 3424
http://www.robertnagle.info