Mobileread
ETI eBook Publisher : bug reports / workarounds / update requests
#1  zelda_pinwheel 03-24-2008, 08:34 PM
while we were discussing workarounds for a bug in eBook Publisher program in a different thread, we thought it might be constructive to pool our knowledge in one single thread. we are also hoping this thread will catch Garth Conboy's eye for hypothetical future versions of the application.

This thread is for :

1. reporting bugs in the soft
2. sharing workarounds
3. suggestions for improvements, for (hypothetical) future versions.


To keep it easy to navigate, maybe use the title of the post to indicate what bug / workaround / feature request you're talking about.
Reply 

#2  zelda_pinwheel 03-24-2008, 08:37 PM
the USABLE screen size of the eb1150 (for a full-screen image, for example), is approximately 310 x 430 px, taking into account the space taken up by running headers in "smallfont" or size "small" text, and small side margins.
Reply 

#3  DaleDe 03-24-2008, 08:55 PM
I have a whole list of requests for improvements in eBook Publisher on my web site.

Dale
Reply 

#4  zelda_pinwheel 03-24-2008, 09:08 PM
if you place an image in your book, which is larger than the maximum screen size of 310 x 430 px (for a 1150 .imp), eBook Publisher will automatically scale the image to fit the screen.

BUG : it will only scale horizontally, not vertically. this means, if your image is tall and narrow, it will fill the screen from side to side but the bottom will be cut off.

WORKAROUNDS : found after much discussion over here
1. resize your image to 430 px max height (for 1150). this is the cleanest solution, especially if you are *only* making an eb1150 version .imp file.

OR

2. add empty side margins to your file, so that it is PROPORTIONAL (homothetic) to the max 1150 screen size of 310 x 430. this can easily be done in Photoshop or other image-editing software, including with batch treatment. THE KEY IS TO RESPECT THE HEIGHT:WIDTH RATIO ; size is immaterial. see practical method below.

NOTE : this workaround will allow you to use the same set of images for the creation of an eb1150 AND 1200 version .imp file, provided that in the 1200 version you add 2ems of margin to the left and right of each full-screen image.

PHOTOSHOP WORKFLOW FOR THIS METHOD :
1. open the image you want to resize (img1).

2. create a "dummy" image* (File>newfile) of 310 x 430 px.

3. select img1, and open the image size dialogue box (ctrl + alt + i). copy the current HEIGHT (ex : 800px), cancel.

4. select dummy image* : open image size, verify that the dimensions are linked ("scale proportionately"), paste the height of other image (800px). The dummy image will automatically be resized. Copy the resulting adjusted WIDTH (for 800px height, width will be 577px), cancel.

*The dummy image is only to simplify things by letting Photoshop do all the math. if you like calculating things, by all means skip the dummy image and figure it out yourself.

5. back to img1, canvas size (ctrl + alt + c), verify that the canvas will be enlarged from the center out and fill color is white, paste new WIDTH (577px), OK.

You can also make a photoshop script for automating this process, if you have a lot of images which are all close to the same height (best results if images have less than 20% variation in height). If height varies wildly, FIRST average out heights by reducing the images (constrain proportions) to the same height.

If you are making an imp 1200 version as well, add 2 em margins to the left and right of each image. you can easily do this by editing the html code of your 1200 version and doing a search and replace (ctrl + H) :
for example, search ><img (the end of the opening p or div container tag, the beginning of the opening img tag)
replace with style="margin-left:2em; margin-right:2em"><img

i recommend doing all the code cleanup on the 1150 version *first* ; then save the html / opf, make the book, close. then MAKE A COPY of the html file adding "_1200" to the filename. then you import this file into the _1200 opf which mobi2imp has conveniently created for you, instead of the original html, and add all the margins to the images. this way, you have 2 separate files to address the different format, but you only do the work once.
Reply 

#5  zelda_pinwheel 03-24-2008, 09:09 PM
Quote DaleDe
I have a whole list of requests for improvements in eBook Publisher on my web site.

Dale
by all means, add the link to this thread. here we can all collaborate and also offer workarounds and solutions we have found.
Reply 

#6  nrapallo 03-24-2008, 09:13 PM
I was converting some .prc to .imp recently and came across a situation where eBook Publisher died without so much as a good-bye!

The culprit is reproduced here (in bold):
Code
<html>
<head>
</head>
<body>
<p>Html documents with this entity &# 20; bomb! No output produced by eBook Publisher v2.2.5</p>
</body>
</html>
Note for display purposes, I put a space between '#' and '2' which should be removed!

I think the author of the .prc wanted to use spaces HTML code '&# 32;' and typed the hex code 20 instead.

BTW, HTML char codes are the &words; used to represent specific characters, for example:
Code
 '&' is represented by '&#amp;'
© is represented by '&#copy';
See the HTML Characters wiki for more information or Special Characters wiki for more advanced uses.
Reply 

#7  zelda_pinwheel 03-24-2008, 09:14 PM
BUG : you cannot specify a margin (or padding) for the "img" tag, either in the css in the head of the document, or inside the individual img tags.

WORKAROUND : add the code using the "style" tag to the container (p or div tag), for example :
<p style="margin-left:2em; margin-right:2em"><img border="0" hspace="0" src="img1.jpg" /></p>

The obvious disadvantage being that you must treat each image individually, rather than just adding one line of css code to the head of your document.
Reply 

#8  nrapallo 03-24-2008, 09:18 PM
I have issues with the href links being case sensitive:

<a href="#WORD">link</a> cannot find <a name="Word"> later on in the html code.
Reply 

#9  nrapallo 03-24-2008, 09:33 PM
Quote zelda_pinwheel
BUG : you cannot specify a margin (or padding) for the "img" tag, either in the css in the head of the document, or inside the individual img tags.

WORKAROUND : add the code using the "style" tag to the container (p or div tag), for example :
<p style="margin-left:2em; margin-right:2em"><img border="0" hspace="0" src="img1.jpg" /></p>

The obvious disadvantage being that you must treat each image individually, rather than just adding one line of css code to the head of your document.
Likewise, for <p> the margin-bottom is simply ignored. The margin-top needs something to "push-off' like a <div>&zwnj;</div>. This bug has been around for a long time and is discussed in the Stylesheets chapter of the 'REBTestDocSrc.imp' posted here.
Reply 

#10  nrapallo 03-24-2008, 10:11 PM
BUG: Missing fraction support for say one-half or three-quarters

WORKAROUND: The &frasl; character allows you to create fractions that flow more proportionately with the surrounding text.
Quote
1/2 vs. <sup class="frac">1</sup>&frasl;<sub class="frac">2</sub> and
3/4 vs. <sup class="frac">3</sup>&frasl;<sub class="frac">4</sub>
- another method using small text yields 1/2 or 3/4:
Quote
<small>1</small>&frasl;<small>2</small> or
<small>3</small>&frasl;<small>4</small>
- and another method using a mixture yields 1/2 or 3/4:
Quote
<sup>1</sup>/<small>2</small> or
<sup>3</sup>/<small>4</small>
- and another method using a mixture yields 1/2 or 3/4:
Quote
<sup>1</sup>&frasl;<small>2</small> or
<sup>3</sup>&frasl;<small>4</small>
- and another simple method using just <SMALL> yields 1/2 or 3/4:
Quote
<small>1/2</small> or
<small>3/4</small>
Reply 

  Next »  Last »  (1/4)
Today's Posts | Search this Thread | Login | Register