James, This book has LOTS of family tree tables and unfortunately the text of the book refers to them. They are really needed in the Plain Text version of the book. They are unnecessary in every other format, but RST does not give me a way to eliminate them in the other formats. I believe in the value of the Plain Text format, so I want to do my best with it. I chose RST because in my earlier donations I found that I would have a lot of corrections to make after I generated the HTML version, no matter how careful I was. I also like that the RST generated books have a consistent look, automatically give you a table of contents and simplify putting in footnotes. RST also does a much better job of creating EPUBs than just submitting a web page would. It breaks up the EPUB files by chapter, for one thing. The PDF problem with the images is a bug. If I didn't use RST I would not get a PDF at all, so I can live with the PDF being imperfect. I don't consider PDF to be an e-book format. On the other hand, if you could get it sized to work for submission to CreateSpace (6" x 9" trade paperback with the required margins, TOC with real page numbers) then you'd have something! If RST had a few new features it would be perfect for the Bhagavata Purana: 1). A feature that says "only put this block in the Plain Text versions". That way you could use ASCII art as a substitute for diagrams that would be images in all other formats. 2). A way to rotate images for EPUBs. The long side of the image would be vertical, for better reading on e-book readers. As an alternative, allow images already rotated that way in HTML. 3). A way to represent a table as an image but use the HTML table for the web page version would be helpful too. I share your frustration that we can only submit Plain Text and HTML and have to live with automatically generated EPUBs from HTML. I see RST as a way to improve the situation, eventually. James Simmons On Mon, Apr 9, 2012 at 3:21 PM, James Adcock <jimad@msn.com> wrote:
*>*My RST file is UTF-8 and has a first line showing it as such. I do have the char set I want, so I'm not sure what you're getting at.
****
Never mind, I see it now – 1.0.txt is your UTF-8 encoding.****
I haven't tried using Adobe Digital Editions, which I assume is what you mean by ADE. I know the ASCII family trees will look like crap in pretty much any e-book reader other than the plain text reader I wrote for the One Laptop Per Child project****
Okay, but why submit something that people can’t actually read?****
Any problems with the non-image versions of the e-books must be caused by the epub generator. I'm just submitting an RST file with images in a subdirectory.
****
Okay, but there are certainly ways of doing what you want to do successfully. Why choose a method which is not successful, and then blame the tool?****
For the PDF it looks like the images are present in the document when you click on the link to the PDF but when you download the PDF and open the downloaded file you don't get the images. Looks like a problem with the PDF generating code.
****
Again, you chose the tools you used to make your e-book.****
** **
_______________________________________________ gutvol-d mailing list gutvol-d@lists.pglaf.org http://lists.pglaf.org/mailman/listinfo/gutvol-d