Using bullet point image in EPUB

[increase]

I am using bullet point images and used
<img src="../Images/Bullet_point_blue.png" width="20" height="20" align="text-top" style="font-size: 1em; text-indent: 0em;"/>

But Sigil does not like the align, how can I wrap the text after the bullet image so that is is centered properly?

[DiapDealer]

Nothing to do with Sigil. Sigil neither likes nor dislikes the alignment.

EPUB, however, does not allow the use of 'align="text-top"' in general. It's not valid xhtml.

Moving this to the Epub forum.

[Quoth]

Best to define a css style and use that either in p, span, div or img tags as appropriate.

[increase]

Originally Posted by FrustratedReader

Best to define a css style and use that either in p, span, div or img tags as appropriate.

Yes you are right, so for anyone else, it was this

<img class="”imgLeft”" src="../Images/Bullet_point_blue.png" width="20" height="20" style="font-size: 1em; text-indent: 0em;"/>

and css add
imgLeft {

float: left;

padding: 5px;

width: 30%;

height: auto;

display: block;

}

[RbnJrg]

Originally Posted by increase

I am using bullet point images and used
<img src="../Images/Bullet_point_blue.png" width="20" height="20" align="text-top" style="font-size: 1em; text-indent: 0em;"/>

But Sigil does not like the align, how can I wrap the text after the bullet image so that is is centered properly?

You are employing a completly wrong code. You should use the css property "list-style-image". For example:

ul {
  list-style-image: url("../Images/Bullet_point_blue.png");
}

Try that.

Regards

[Quoth]

Sometimes in a ebook it's better to use user constructed fake lists without the ul and related list elements. I'd always use the ul approach on a website.

[DNSB]

Originally Posted by increase

I am using bullet point images and used
<img src="../Images/Bullet_point_blue.png" width="20" height="20" align="text-top" style="font-size: 1em; text-indent: 0em;"/>

But Sigil does not like the align, how can I wrap the text after the bullet image so that is is centered properly?

Out of curiosity, what units are you using for width and height? 20 is meaningless without the units (cm, px, pt, whatever) or %. Using absolute values (width=20px for example) is bad since the image can be overlarge on a low resolution screen and too small on a high resolution screen. Check any decent site for the width and height properties.

[hobnail]

Originally Posted by FrustratedReader

Sometimes in an ebook it's better to use user constructed fake lists without the ul and related list elements.

But when?

[DNSB]

Originally Posted by hobnail

But when?

Pretty much anytime that a list is used.

[Turtle91]

Originally Posted by DNSB

Pretty much anytime that a list is used.

I would amend this statement slightly.... Pretty much anytime that a list is used IF your targeted selling platform has issues with list items.

That requires a little research to determine. The safe route would be to manually build the non-list. I'm more of a rebel however. I would use the standard html tags as designed. They are supposed to be supported in a standards compliant device/app. If customers complain, then the fault can be laid at the foot of the device/app maker to support the standards. It is only by this method that they will be pushed to maintain standards. Of course, I don't have to deal with pesky little things like customers and sales...

[hobnail]

Originally Posted by DNSB

Pretty much anytime that a list is used.

Of course I forgot to add, "but why"?

Does the EPUB spec say what to use for the nav.xhtml in an EPUB 3? Sigil is using ol/li. I always use that nav.xhtml for the book's TOC that the user sees, by opening it in calibre's editor and dragging the nav.xhtml to the front of the book (doesn't work in sigil for whatever reason; it stays at the end).

I've used dt/dd for glossaries without any problems. I agree with Turtle91. (Let them eat cake!)

[DNSB]

Originally Posted by hobnail

Of course I forgot to add, "but why"?

Does the EPUB spec say what to use for the nav.xhtml in an EPUB 3? Sigil is using ol/li. I always use that nav.xhtml for the book's TOC that the user sees, by opening it in calibre's editor and dragging the nav.xhtml to the front of the book (doesn't work in sigil for whatever reason; it stays at the end).

I've used dt/dd for glossaries without any problems. I agree with Turtle91. (Let them eat cake!)

I have two separate methods for working on ebooks. For myself, I'll use whatever I want as long as I can make it look good on my ereader collection. This is very different from when I am working on an ebook for another person, I tend to go as vanilla as possible to improve the chances of the book looking, if not good, at least readable on as many devices as possible.

As for nav.xhtml and lists? The spec is publicly available so you may want to check 5.4 EPUB Navigation Document Definition which does specify the use of ol/li elements.

Given that most of the associated text is rather short ( a short single line), there shouldn't be some of the issues I've seen with lists with multiline/multiparagraph text. Then there have been the times I've run into the use of nested lists. That use tends to end rather badly for all concerned.

[DNSB]

Originally Posted by Turtle91

They are supposed to be supported in a standards compliant device/app. If customers complain, then the fault can be laid at the foot of the device/app maker to support the standards. It is only by this method that they will be pushed to maintain standards. Of course, I don't have to deal with pesky little things like customers and sales...

Amazon. 'Nuff said!

[Hitch]

Originally Posted by DNSB

Amazon. 'Nuff said!

Yes...for which, faux lists never work right. Only bog-standard uls and ols can be relied upon to work in KF7, KF8 and KFX.

If you substitute a character, an icon, a bullet, or some funky thing like hearts, flowers, wee piglets (yes, really), the hang is never, never right. MOBI (in toto) does not like a faux-list-constructed hanging indent and it only aligns perfectly at one font size.

You can get away with it in ePUB--but not in MOBI and honestly, I never--never--recommend reconstructing a list rather than the standard HTML if we can help it for that reason. My inner control freak gets whingey when the hanging indent isn't perfect.

Hitch

[DNSB]

Originally Posted by Hitch

Yes...for which, faux lists never work right. Only bog-standard uls and ols can be relied upon to work in KF7, KF8 and KFX.

If you substitute a character, an icon, a bullet, or some funky thing like hearts, flowers, wee piglets (yes, really), the hang is never, never right. MOBI (in toto) does not like a faux-list-constructed hanging indent and it only aligns perfectly at one font size.

You can get away with it in ePUB--but not in MOBI and honestly, I never--never--recommend reconstructing a list rather than the standard HTML if we can help it for that reason. My inner control freak gets whingey when the hanging indent isn't perfect.

Hitch

Not to mention the cases of readers who complain to Amazon and then the author gets told their book is being pulled until the formatting or typographic errors are corrected. In one case, the "typos" being complained about were the use of Canadian/British alternative spellings. Then we have Amazon's automated checking which seems to be more than a bit arbitrary at times. In the one case I was involved with a few years back, there seemed to be little information on exactly what triggered the warning message.