James, I figured out the backlink problem. I use backslashes in my ASCII art family trees. I'm going to have to stop doing that. James Simmons On Mon, Apr 9, 2012 at 11:32 AM, James Simmons <nicestep@gmail.com> wrote:
James,
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.
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:
http://activities.sugarlabs.org/en-US/sugar/addon/4035
The larger image files would look a lot better on a e-book reader if they were rotated but the PG guidelines don't allow that.
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.
I may replace the big table in the e-book version I will eventually make for Amazon and Nook with a page image.
I'll check out that backlink message and the 1O thousand sons.
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.
It would be nice to have some kind of RST markup that says "put the following in the text version only". That would be a big help with the family trees.
James Simmons
On Sun, Apr 8, 2012 at 11:09 PM, James Adcock <jimad@msn.com> wrote:
*>*but I'm still interested in any comment from you all.****
** **
Don’t understand why you didn’t do a UTF-8 txt version so that you can get the char set that you want?****
** **
Not sure your intent, but the family trees certainly don’t render “correctly” in ADE.****
** **
ADE page numbers overlap text.****
** **
Nit: some paragraphs are indented after a title heading, others are (correctly) flush left.****
** **
Images fail to display in the non-image version when viewed in Kindle Previewer, with an apparent indication that Kindle Previewer considers the image files to be corrupt, whereas in the non-image version I would expect the image files to be silently redacted, rather implementing in some kind of “fail mode.”****
** **
Images fail to display correctly in the image version when viewed in Kindle Previewer in Kindle Fire mode, with aspect ratio not being maintained.****
** **
Family trees don’t display correctly in Kindle Previewer.****
** **
Many tables are way too wide to be successfully viewed on ebook readers, which realistically can only support about three columns.****
** **
MOBI version contain the error message:****
** **
file:///htdocs/epubmaker/cache/21....bpurana.rst, line 5111); backlink*** *
** **
1O thousand sons, presumably meant to say: 10 thousand sons****
** **
PDF version gives indication that the image files are corrupt rather than displaying the images.****
** **
_______________________________________________ gutvol-d mailing list gutvol-d@lists.pglaf.org http://lists.pglaf.org/mailman/listinfo/gutvol-d