Quote:
Originally Posted by rogue_ronin
Also, it's a class so if you have more than one image in this class in a book, they will all be resized the same. Adding a class for every image is probably overkill.
Now, if you are only using one image, ever, you're okay -- but will have to manually recode each book.
m a r |
I think we have three issues here - hard coding the cover jpg into the HTML, manually changing the dimensions, and using more than one image.
The very few ebooks I've prepared have been done for Mobipocket format with Mobipocket Creator and/or Calibre. Both have the option/requirement of specifying the cover image separately, and 'bind' it to the ebook. I'm used to that process, and have not thought of (and don't see the need) to hard code it into the HTML. I'm still learning, and recognise that things may change when I become able to do ePub or other formats.
I don't expect at the moment to have more than one image in an ebook, so it's no great shakes to manually change the width and height.
The markup I use is taken directly from some web pages I have done and manages images of different sizes on the same page.
One example is
http://citybaptistchurch.net/Iraq.htm