OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.

 


Help: OASIS Mailing Lists Help | MarkMail Help

docbook-apps message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]


Subject: Re: [docbook-apps] Template of what can go into the info element of an EPub book


To answer my own question I went through the file and found the following child elements of info that have templates in epub3

authorgroup
author
corpauthor
editor
othercredit
corpcredit
collab
date
pubdate 
abstract
subjectset
subjectterm
keywordset
keyword
publisher
publishername
bibliocoverage
bibliorelation
bibliosource
copyright

Carlos

On Apr 20, 2012, at 2:09 AM, Bob Stayton wrote:

> Hi Carlos,
> There are no DocBook info elements that are not allowed, only elements that are not used in the output. Some info elements are displayed on the HTML title page, some are copied as metadata to the EPub .opf file, and some are not output at all.
> 
> You can customize what elements appear on the title page using the titlepage spec mechanism described in my book:
> 
> http://www.sagehill.net/docbookxsl/HTMLTitlePage.html
> 
> If you are talking about which info elements are currently supported in the Epub .opf file, then that still remains to be documented. I can tell you how it works, though.
> 
> In the epub3/epub-element-mods.xsl file, there is a template named 'metadata.other.info' that does this:
> 
> <xsl:apply-templates select="$info/*" mode="opf.metadata"/>
> 
> There are several templates in that file that use that mode to generate <meta> elements, such as:
> 
> <xsl:template match="publisher" mode="opf.metadata">
>    ...
> 
> There is also an empty wildcard template to handle any info elements that don't have such a template:
> 
>  <xsl:template match="*" mode="opf.metadata"/>
> 
> You can peruse that file to find the templates that use that mode to see which info elements are currently supported.  Any suggestions for additional elements that should be supported would be appreciated.  Adding support for custom elements requires creating a template in that mode in your customization layer to output an appropriate <meta> element.
> 
> I'll try to add the list of supported info elements to the epub3/README file for the 1.77 release.
> 
> Bob Stayton
> Sagehill Enterprises
> bobs@sagehill.net
> 
> 
> ----- Original Message ----- From: "Carlos Araya" <carlos.araya@gmail.com>
> To: <docbook-apps@lists.oasis-open.org>
> Sent: Thursday, April 19, 2012 8:35 PM
> Subject: [docbook-apps] Template of what can go into the info element of an EPub book
> 
> Good evening:
> 
> Is there a template of what I can use in the info element of a book to be published as EPub 3?
> 
> Is there a guide of which, if any, elements are not allowed?
> 
> Carlos
> 

Attachment: signature.asc
Description: Message signed with OpenPGP using GPGMail



[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]