On 17 February 2010 13:10, Greg Baryza <baryza@intersystems.com> wrote:
> I'm still very much a newbie when it comes to ePUB, so if these comments are
> off the mark, I welcome the educational opportunity...
>
> Drawing a line between XHTML and ePUB seems like making a distinction
> without a difference.
Subtle, but important differences.
 Isn't the browser "flowing" content  into the page in
> a way similar to that of an eReader?
Yes, i.e. doing the layout from 'semantic' markup.
 It appears that many of the current
> conversion-to-ePUB products take PDFs as input so why not cut out the middle
> step when you can work with the original markup?
Appears? I'd question that. I'd say that's like taking a presentation
and saying you want it in another 'presentation' format
A better workflow is to go from real semantic markup (some
XML vocabulary) and transform into an output format,
e.g. via xslt+xsl-fo then use XEP to get to PDF
e.g. via xslt to get to e-pub
>
> We have used XEP quite satisfactorily for half a decade now. Â We are
> starting to get probes from our current customers as to whether we will
> produce the content for their eReaders, or whether they will have to do it
> themselves. Â Naturally, we would rather produce the content.
'transform' the content? If their source is semantically marked
up XML then you've an easy task.
HTH
-- Dave Pawson XSLT XSL-FO FAQ. Docbook FAQ. http://www.dpawson.co.uk ------------------- (*) To unsubscribe, send a message with words 'unsubscribe xep-support' in the body of the message to majordomo@renderx.com from the address you are subscribed from. (*) By using the Service, you expressly agree to these Terms of Service http://www.renderx.com/terms-of-service.htmlReceived on Wed Feb 17 06:08:39 2010
This archive was generated by hypermail 2.1.8 : Wed Feb 17 2010 - 06:08:46 PST