Style Sheet entry for a 'hanging' style

[AThirstyMind]

p.FlushHang, li.FlushHang, div.FlushHang
{mso-style-name:FlushHang;
margin-top:0in;
margin-right:0in;
margin-bottom:0in;
margin-left:0in;
margin-bottom:.0001pt;
text-indent: -.25in;
font-size:12.0pt;
font-family:"Times New Roman",serif;}

The above is what shows up when I format a line (flush left) to hang at 1.5em on the second line. Please disregard the 'in' and 'pt' designations... I edit these to 'em' before converting.

Anyway, the above style doesn't work... it indents the first line a negative 1.5em and not the second line. So how should I construct this style so it comes out:

First line flush
and Second line indented 1.5em

I thought I'd done this before with good results, but now I don't remember which book included this hanging style. This specific style is used in a glossary.

Thanks!

[Notjohn]

I have this information in my files. Dunno who provided it. (Hitch, perhaps. "Pesky" is her sort of word.) Hope it's useful!

Hanging indents will work in both KF6 an KF8 if you use a media �
query in CSS something like:

@media amzn-kf8
{
p.hang { text-indent:-36; margin-left:36;}
}

and use the following code in the body of the HTML file:

<p class="hang" width="-36">Your text here.</p>

The negative text-indent works in CSS for Kindle 2 (and later KF6 �
devices) but only without the margin-left attribute. With �
Amazon's latest epublishing tools this coding produces cut-off �
text in KF8 (you need that pesky margin-left).

[JSWolf]

Originally Posted by Notjohn

I have this information in my files. Dunno who provided it. (Hitch, perhaps. "Pesky" is her sort of word.) Hope it's useful!

Hanging indents will work in both KF6 an KF8 if you use a media �
query in CSS something like:

@media amzn-kf8
{
p.hang { text-indent:-36; margin-left:36;}
}

and use the following code in the body of the HTML file:

<p class="hang" width="-36">Your text here.</p>

The negative text-indent works in CSS for Kindle 2 (and later KF6 �
devices) but only without the margin-left attribute. With �
Amazon's latest epublishing tools this coding produces cut-off �
text in KF8 (you need that pesky margin-left).

That's wrong. You do not need to add width=36 to the HTML. You should never add CSS code to the HTML. Put the code in CSS and use the CSS classes.

[AThirstyMind]

Thanks, I wondered if perhaps the rules had changed. But I think I'll go a different way for this glossary, something simpler with maybe 0.5em between each entry instead of the 'pesky' hanging line.

[GrannyGrump]

@AThirstyMind ---

For a glossary, have you ever tried using <dl> definition list? That automatically keeps the term <dt> aligned to the left margin, and insets the definition <dd> like a hanging indent. You can set attributes for bold, italic, top and bottom margin, alignment (left, center, right, justify).

I used this for some glossaries I added to children's books, and it was SO much easier than working with a "hanging indent" as I have used in the past.

Take a look at "Oswald Bastable" or "Phantasmion" if you are interested in the css.

https://www.mobileread.com/forums/sho...ight=bastables

https://www.mobileread.com/forums/sho...ht=phantasmion

[Hitch]

Originally Posted by Notjohn

I have this information in my files. Dunno who provided it. (Hitch, perhaps. "Pesky" is her sort of word.) Hope it's useful!

Hanging indents will work in both KF6 an KF8 if you use a media �
query in CSS something like:

@media amzn-kf8
{
p.hang { text-indent:-36; margin-left:36;}
}

and use the following code in the body of the HTML file:

<p class="hang" width="-36">Your text here.</p>

The negative text-indent works in CSS for Kindle 2 (and later KF6 �
devices) but only without the margin-left attribute. With �
Amazon's latest epublishing tools this coding produces cut-off �
text in KF8 (you need that pesky margin-left).

I agree that pesky is my kind of word, but, I never have used the KF6 appellation. (Even though it was technically correct).

I do recall that for a while--and this was a while ago--we had to do exactly what you have there, but we've never used something like -36, either. We've used ems and/or percentages for dog's years...at least since '09. So...I'm going to say that's from Charlie. (Who did use KF6 as his term.) That's my guess.

We did have to set the margin offset, because there was a problem with...hmmm...Fires? Some of the readers, if you weren't careful with the offset, would literally have that first line of text running off the page on the left-hand margin. Nasty. But, man, that's been a WHILE. I don't remember it that clearly, now.

@Thirsty? Do you still need hanging indent css? I can dig ours up and get that to you, if you do?

Hitch

[AThirstyMind]

Hitch... yes I would like the hanging indent css. Thanks. Although for this book's glossary I used another style. But I'd like to have that in my repertoire.