>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.