Keith,
I agree with you that the output should not be tailored for an intermediate
converter. The converters ought to be set up to work with clean epub.
Of course, at this point, it's unfair to expect these epub2 converters to do a
good job on epub3, although, Calibre did a surprisingly good jo
Hi,
Thank you for providing clear testing results, Dick.
(Speaking only for myself...)
I feel *very* strongly that the DocBook-XSL EPUB 3 output that Bob is
working on (with support from O'Reilly Media) should not be limited by
either kindlegen or calibre. I do not feel that criticisms based on
Bob,
I just tried the epub3 beta 3 transform and was able to successfully process a
250+ page book with toc, index, figures, tables, etc.
I then fed the book to Calibre, converted it to mobi, and tried both mobi and
epub on my iphone. While I haven't (yet) extensively tested the files, both
lo
On 4.10.2011 20:29, honyk wrote:
> Recently there were some rumors...
> http://goodereader.com/blog/tablet-slates/amazon-to-allow-epub-ebooks-on-the-kindle-e-reader/
Kindle 4 I have received yesterday doesn't recognize EPUB.
Jirka
--
On 4.10.2011 17:49, Bob Stayton wrote:
>
>
>
>http://www.w3.org/1999/xhtml
>
> and it seems to add
>
> xmlns="http://www.w3.org/1999/xhtml";
>
> in the right place. That seems too easy. I'm used to doing all kinds
> of contortions to get namespaces correct. But I guess in this cas
I can confirm that if you use the -ns- version of the stylesheets, the epub3
(beta2) stylesheets don't work. I forget the exact nature of the error message
you get, except that it was not 100% obvious what the problem was:-).
I was able to process DB5 (a relatively long book) using epub3 and the
> Yep, it's crappy Amazon who is not supporting EPUB directly and who
> produces this crappy KindleGen software. But it would be nice to produce
> EPUB files which can be smoothly converted into format supported by
> most widespread reader today.
Recently there were some rumors...
http://gooderead
Hi Jirka,
I just tried changing the following template in template/titlepage.xsl:
http://www.w3.org/1999/xhtml
and it seems to add
xmlns="http://www.w3.org/1999/xhtml";
in the right place. That seems too easy. I'm used to doing all kinds of contortions
to get namespaces correct.
Hi Jirka,
I ran into this same problem when creating the beta epub3 stylesheets. I had to add
some templates for isbn, issn, and biblioid for epub metadata, so I needed to include
an updated titlepage.templates.xsl in the beta distribution. For the beta, I admit I
just edited it by hand afte
Hi Tim,
You are correct that there is no syntax in Epub2 to link from one Epub to another.
External linking for Epub3 is still under discussion and not included in the draft
standard, as far as I can tell. The general solution is difficult because of
uniqueness, file locations, etc.
However,
Hi,
I'm not quite clear which you are asking for, as the subject line says
"titlepage-on-separate-page" and the body says TOC on its own page. I'm also not
clear if you mean FO output and separate physical pages, or HTML output and separate
chunk pages. In general, the more detail you put in
On 4.10.2011 15:46, Adam Witwer wrote:
> "" Aug 1 2011 Update. I have resigned myself to the need to do some
> post-processing of HTML code after the epub is generated. ""
>
> We take this same approach at O'Reilly (using XSLT that we maintain),
> and there's no reason to think we won't have to
On 4.10.2011 15:16, Jirka Kosek wrote:
> When I convert with calibre all headings (chapter, section, table, ...)
> are lost.
OK, problem were in titlepage.templates.xsl file. This file was missing
xmlns="http://www.w3.org/1999/xhtml"; and thus generated in the middle of XHTML5 output which confu
On 30.9.2011 13:34, Bob Stayton wrote:
> Hi,
> I have updated a beta 3 version of the epub3 stylesheets for DocBook
> XSL to SourceForge. It is in this directory:
>
> https://sourceforge.net/projects/docbook/files/epub3/
Hi Bob,
have you tried to convert resulting EPUB into MOBI format for use
Is there an equivalent XSL parameter, so that a TOC element is on it's
own page? Or do I need to create a title page spec file and generate
a custom XSL template for this purpose?
Thanks,
Lars
-
To unsubscribe, e-mail: docbook-ap
15 matches
Mail list logo
