Carlo>Jim, are you happy with the epubs and mobi generated through RST, any of these PG numbers: Well, if you ask me "any" of these numbers I will just look at one of each if you don't mind. RST 34605 is a junior reader, which usually doesn't exercise the full set of problems one sees in an adult book, but, let me continue. The HTML version has wide margins, which will tend to make PG customers unhappy when they access this file via a web browser from a small device, like an Android tablet. The HTML version doesn't show page numbers, but the EPUB version does -- so I don't understand how you manage to do that? The EPUB version seems to somehow have the margins trimmed. Did Marcello's software trim the margins for you? Now "magically" there are page numbers in the small right hand margin which didn't exist in the HTML version. I don't understand how this is possible? If PG requires that submissions for EPUB and MOBI version be via HTML, then how is this possible? I'm sure I don't know. The EPUB version is something I could live with, IE I think it is "readable" on most EPUB devices, even though personally I would prefer not ragged right, not having a small right hand margin, and not having page numbers there -- at least not in a junior reader. But still the EPUB is successful enough that I don't consider it embarrassing. I just don't know how it can be "magically" -- if PG requires EPUB and MOBI to be via HTML submission -- how this file ends up with page numbers but the HTML version does not? The MOBI version needs to be looked at in two different ways 1) under a "traditional" Kindle device and 2) in a "Kindle Fire" new generation device. Under Kindle Fire: It seems like you have a way to not use the "Blue PDA" as the cover image. I don't see how you do this, because I don't see how PG allows specification of the cover image to be used with an HTML submission? In any case, on many small devices a cover image like you have which includes title and author is much more useful than the PG default "Blue PDA." Or is it that you don't include a cover at all, and that Amazon is automagically providing me with one? But when I submit an HTML PG gives my EPUB a "Blue PDA" -- whether I want it or not! Title Page images are margin left, in HTML they are centered. Is it possible that image location isn't being specified and is just picking up the web browser defaults? Hitting "Back Link" on a chapter title takes one to a scrambled version of the TOC, which is presumably related to MOBI file lazy evaluation. Is your TOC link target placed *after* the format specification for the TOC? MOBI might work better if the TOC link target is placed *prior* to the TOC format specification, if possible. You are doing "no margins-top, first line indent" on paragraphs, I find it easier one small devices to read "1em margin-top, first line no indent" on paragraphs, but this is mainly a personal preference item. "CHAPTER V: JANET HEARS FROM BETTY" title formatting is not very successful. It would probably format better if you specified this as: CHAPTER V JANET HEARS FROM BETTY IE Chapters with titles in two lines, each line centered. Many of the chapter titles suffer appearance from the choice of implementation. "But when the old woman got home in the dark," etc. This poem formats poorly due to poem line break problems. Not to imply that I personally know a good solution to "HTML" based poetry formatting. But it does seem like you could easily choose to indent poems much less than this, leading to poem linebreak problems less frequently. "Bye little Betty, ..." seems to be indented *way* too much. "THE END" and subsequent PG "advertisements" are formatted poorly. It would be nice if the reader could savor finishing the book for a few moments before being immediately hit by the "pgegalize." Put in a page break before the "pgegalize" ? ----- "Traditional Kindle" : Seems to have the same exact issues as "Kindle Fire" -- which is encouraging, given that presumably PG is still compiling "HTML" to MOBI7 using the previous version of Kindlegen, and not the "KF8" using the current generation of Kindlegen. Picking TEI 34520 "at random" -- just to have a book of a similar vintage to RST 34605 -- I see: The HTML version (reading HTML on a small device): has wide margins, which will tend to make PG customers unhappy when they access this file via a web browser from a small device, like an Android tablet. Page numbers are rendered in the left margin, which probably explains why the margins were set so wide. Page numbers 2 and 3 are rendered literally exactly on top of each other which presumably is a TEI->HTML implementation bug. "PGegalize" is formatted no-wrap mode so it runs ugly off the right hand of the screen. Not clear why the "PGegalize" is placed at the front of some (RST) books and at the end of others (TEI) ? Excess margins in the TOC causes more entries than necessary to wrap unattractively. And in general the TOC is hard to read since it wraps so much (and many times a single entry over multiple lines) which again is due to excessive margins. Images are not set to scale correctly to fit the (small) device page size so that on a small device one only sees a tiny upper left corner nibble of the images. <p> formatting is chosen to be 1em spacing between paragraphs, no paragraph indent, which personally I prefer because I think on small devices it is somewhat easier to read. [pg 014] doesn't fit the margin so it renders: [pg 0 14] And where the "]" somewhat overlaps the first letter of the body text. Same for all margin page numbers, basically. Topic titles are formatted "Margin Left" rather than centered, as I would expect of a traditional book. If this were a computer manual instead of a biblical manual, then I would expect to see topic titles formatted left ala K&R troff style. "Note.-God did this by backing His promises with an oath based upon Himself. Heb. 6:13, 14. By this He pledged and placed at stake His name, or character, for the fulfillment of His word." -- which actually looks even worse on the small web browser than I have represented above since the formatting has been chosen to try to "justify" making the gaps between the above words go all over the place. But the point being when you start using "big" margins on small device the results are necessarily tragic. In this case were the left and right margins needlessly set in ems or something, instead of using % ? O Word of God incarnate, O Wisdom from on high, O Truth unchanged, unchanging, O Light of our dark sky! We praise Thee for the radiance That from the hallowed page, A lamp to guide our footsteps, Shines on from age to age. Shows a "textbook example" of the difficulty of HTML "poem" formatting especially on small devices when large margins and indents are chosen. [The actual poem, should you fail to recognize what it should have been, is:] O Word of God incarnate, O Wisdom from on high, O Truth unchanged, unchanging, O Light of our dark sky! We praise Thee for the radiance That from the hallowed page, A lamp to guide our footsteps, Shines on from age to age. Index seems very long for a small device. Is this really what was in the original book? End "pgegalize" : While generally readable, the http links have been formatted n-wrap which means one cannot read the whole http link making them generally unusable. EPUB: The ngx or whatever its called seems to be way overpopulated. Page numbers now have magically jumped from the left margin to the right margin and what used to read "[PG 014]" now just reads a small grey "14" -- how do they do that? How does one submit HTML which looks so different in an HTML browser than in EPUB, I wish I knew how they do that? Because I was told if one wants to target EPUB or MOBI the ONLY option is to submit an HTML file. Hm, except now I see a line that says: [pg 002][pg 013] ... 7 So now I am confused: Is this page 2, or page 13, or page 7 ??? Margins seem large for the small device Images do not scale to fit device Some images are compressed using a scheme which does not display correctly on the device. Some page numbers [pg 016] are now showing up in the body text, interrupting the reading, which I personally never think represents a reasonable tradeoff. Same kinds of severe poetry formatting issues makes the poems unreadable. Same kinds of severe left and right margin "indenting" on blockquotes makes them unreadable. Etc. EPUB showing basically the same kinds of extreme problems present when trying to read the HTML on a small device. Credits: The credits are formatted so that they show up farther to the right than the center of the display and therefore of course are badly clipped off by the right edge of the physical display. Kindle: No image versions of the files are provided at all? Did a gen tool silently fail? Or no one bothers to fix gen failures? Kindle Fire: Unfortunately these files have been "successfully" provided with the "Blue PDA" default PG cover image, meaning that one has 20 identical appearing "Blue PGA" PG books on one's Kindle, and one does not know which book is which. Author name is apparently not correctly being provided by TEI because it doesn't show up on Kindles, where sorting on author name is an important choice. Content header runs up against previous formatting. In general all the lead-in pages formatting is incorrectly run-together. And left-aligned instead of centered, but left-aligned against an excessive left margin width. TOC items bulleted, which is uncommon in TOCs, I believe, and looks strange to my eyes. The missing images are replace with the left-aligned words: Illustration. The Word of God.... -- except in reality there is no vertical whitespace being used to offset these words. For accessibility reasons I would think if one takes out the images and replaces them with something that something ought to be a description of that which was left out? No vertical space after subject headings. Traditionally one would expect to see some spacing between a subject heading and the following paragraph. Ideally the first paragraph after a subject heading shouldn't have an indentation. Poems are now miraculously left-aligned without an excessive margin. But the even-numbered poem lines *ought* to be indented relative to the odd-numbered poem lines and how somehow they are not. In general something seems to have swallowed ALL the vertical "whitespace" formatting that *ought* to be there. Everything simply "runs together" vertically. End "pgegalize" is now readable, but something has turned what used to be active http links into inactive text. Credits show up "OK" on Kindle, but somewhat excessively indented (but not as bad as on EPUB) Kindle "Traditional:" TOC Entries: the bullets and the TOC entries show up on different lines in the display looking pretty silly. "How Readest Thou?" This section shows up with some kind of "pre" formatting or something which doesn't wrap correctly, and lines break unattractively. In generally beyond this the Kindle "Traditional" showing the same kinds of problems as Kindle Fire. In general, I would say the this particular TEI is no more successful in practice on a Kindle than simply sending a txt72-unwrapped version of the plain text to a Kindle. If then. Sorry -- Jim