|
View:
New views
4 Messages
—
Rating Filter:
Alert me
|
|
|
ePub: meta informationWhat would be the preferred way to add meta information (like
"dc:description", "dc:identifier", "dc:title", or "dc:language") given that the input file might not contain the necessary information? Should I simply override the "opf" template"? Michael PS: Some TeX guys asked me about how to convert LaTeX files to ePub. My suggestion probably will be to use "tex4ht" to convert the source files to DocBook and further to ePub using the ePub support in the actual DocBook XSL stylesheets. A first attempt was very promising, but the converted DocBook file doesn't contain the (wanted) meta information. --------------------------------------------------------------------- To unsubscribe, e-mail: docbook-apps-unsubscribe@... For additional commands, e-mail: docbook-apps-help@... |
|
|
Re: ePub: meta informationOn Thu, Jun 18, 2009 at 4:49 AM, Michael Wiedmann<mw@...> wrote:
> What would be the preferred way to add meta information (like > "dc:description", > "dc:identifier", "dc:title", or "dc:language") given that the input file > might not contain the necessary information? Sorry, I don't understand where this data would come from. Currently, dc:title comes from $doc.title dc:description comes from the abstract dc:language comes from the l10n.language of the root note dc:identifier comes from an identifier found on /*/*info (look at the template for the options) > Should I simply override the "opf" template"? That would probably be the easiest way. > PS: Some TeX guys asked me about how to convert LaTeX files to ePub. My > suggestion probably will be to use "tex4ht" to convert the source files to > DocBook and further to ePub using the ePub support in the actual DocBook XSL > stylesheets. A first attempt was very promising, but the converted DocBook > file doesn't contain the (wanted) meta information. It may be easier for them to go to XHTML, I dunno. Keith --------------------------------------------------------------------- To unsubscribe, e-mail: docbook-apps-unsubscribe@... For additional commands, e-mail: docbook-apps-help@... |
|
|
Re: ePub: meta informationHi,
On the DocBook side, the following reference to a page in the DocBook 4.2 specification lists the DocBook equivalents for Dublin Core metadata elements: http://www.docbook.org/specs/cs-docbook-docbook-4.2.html#d0e652 If you also need to use Dublin Core qualifiers, then there are attributes on those elements that cover most of the qualifiers listed in the original Dublin Core Qualifiers document. You'd have to investigate how the epub stylesheet handles these. Bob Stayton Sagehill Enterprises bobs@... ----- Original Message ----- From: "Michael Wiedmann" <mw@...> To: "DocBook Apps ML" <docbook-apps@...> Sent: Thursday, June 18, 2009 4:49 AM Subject: [docbook-apps] ePub: meta information > What would be the preferred way to add meta information (like > "dc:description", > "dc:identifier", "dc:title", or "dc:language") given that the input file > might not contain the necessary information? > > Should I simply override the "opf" template"? > > Michael > PS: Some TeX guys asked me about how to convert LaTeX files to ePub. My > suggestion probably will be to use "tex4ht" to convert the source files > to > DocBook and further to ePub using the ePub support in the actual DocBook > XSL > stylesheets. A first attempt was very promising, but the converted > DocBook file > doesn't contain the (wanted) meta information. > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: docbook-apps-unsubscribe@... > For additional commands, e-mail: docbook-apps-help@... > > > --------------------------------------------------------------------- To unsubscribe, e-mail: docbook-apps-unsubscribe@... For additional commands, e-mail: docbook-apps-help@... |
|
|
Re: ePub: meta informationKeith Fahlgren wrote, on 18.06.2009 17:41:
> Sorry, I don't understand where this data would come from. Some of this data might be part of the original Latex file (but might not be converted to appropriate DocBook elements). As a last resort there is always the possibility to add this data using a custom stylesheet (disadvantage: no generic solution). >> Should I simply override the "opf" template"? > > That would probably be the easiest way. OK, I'll try this with one of the more complex sample files. > It may be easier for them to go to XHTML, I dunno. But then we/they have to reinvent the wheel (generate the OPF, NCX file, etc.) - DocBook XSL does already most of the necessary work. Thanks Michael --------------------------------------------------------------------- To unsubscribe, e-mail: docbook-apps-unsubscribe@... For additional commands, e-mail: docbook-apps-help@... |
| Free embeddable forum powered by Nabble | Forum Help |