Sigil superscript line spacing

[ebookscovers]

HI there. very much a newbie with all CSS. see my screenshot of how my superscript looks in Kindle previewer. It's fine. only issue I have is the spacing above the line is too big and needs to be same spacing above without interfering with the superscript. how do I amend this globally? what is the exact code required to fix this AND what do I insert the code. see all screenshots. Help. David

[Turtle91]

Don’t see the image…

Also, can you post the css you are using so we can see where the problem lies?

My initial thought is that you are using line-height inappropriately, but not sure.

[ebookscovers]

thanks. thought I'd uploaded. see attached issue.

[Leonatus]

In french books, with Mme and Mlle frequently superscripted, I found things like this:

sup { 
  font-variant: normal;
  line-height: 0;
}

or this:

.t6 {
    font-size: smaller;
    vertical-align: text-top
    }

That's working quite well for me.

[Hitch]

Originally Posted by Leonatus

In french books, with Mme and Mlle frequently superscripted, I found things like this:

sup { 
  font-variant: normal;
  line-height: 0;
}

or this:

.t6 {
    font-size: smaller;
    vertical-align: text-top
    }

That's working quite well for me.

In a rendered, post-Publishing Workflow, for-sale Kindle eBook? You're not seeing any distinction between the lines above/below superscripted or footnotes lines? Or do you mean in Previewer?

Hitch

[Leonatus]

I have no Kindle, but a Kobo, and don't know if general CSS-rules are applicable.
But in my books, I use something with the line-height: 0;-rule.

[Hitch]

Originally Posted by Leonatus

I have no Kindle, but a Kobo, and don't know if general CSS-rules are applicable.
But in my books, I use something with the line-height: 0;-rule.

Okay, so you're not testing that on a live Kindle, post-publishing, then?

I ask b/c Amazon pretty rgularly and routinely forces the line-heights to be what it wants them to be. The 1.2em-line-height for regular text is a hard-and-fast rule and no matter what you do, in the body text, it won't change to 1.2 o4 1.4 or anything else. (You can do that for small bits of text, don't get me wrong, but not the body.)

And vis: superscripts and the like--the lines above and below, depending, are always shifted slightly, to make room for the (sized) fonts. The lines above move up, to make room for the superscripted text, the tallest character that might exist, in that font with that styling and the subscript does the same thing to the line below.

Beieve me, we've used coding very much like yours, but...it seems to be overridden at the PW.

Same reason that most users cannot make a viable Dropcap. Same exact coding.

Hitch

[ebookscovers]

yes its kindle previewer I used to make sure all looks fine before publishing. I will give drop in the code and see if works. you are right though Amazon tend to override a lot of settings

[JSWolf]

Originally Posted by Hitch

Okay, so you're not testing that on a live Kindle, post-publishing, then?

I ask b/c Amazon pretty rgularly and routinely forces the line-heights to be what it wants them to be. The 1.2em-line-height for regular text is a hard-and-fast rule and no matter what you do, in the body text, it won't change to 1.2 o4 1.4 or anything else. (You can do that for small bits of text, don't get me wrong, but not the body.)

And vis: superscripts and the like--the lines above and below, depending, are always shifted slightly, to make room for the (sized) fonts. The lines above move up, to make room for the superscripted text, the tallest character that might exist, in that font with that styling and the subscript does the same thing to the line below.

Beieve me, we've used coding very much like yours, but...it seems to be overridden at the PW.

Same reason that most users cannot make a viable Dropcap. Same exact coding.

Hitch

I've noticed that the previewer screws with the line-height. So anything that could have an effect on line-height needs a Kindle Reader to do a proper previews.

[JSWolf]

By the way, why is this thread in Sigil when it's talking about Kindle eBooks? It should be in Kindle Formats forum (IMHO).

[ebookscovers]

still the same issue when I put in code. Kindle previewer still pushes line up above the superscript. maybe the best thing going forward is to avoid using superscripts and just write 21st as is??

[ebookscovers]

I'm using Sigil to clean up the code in ebook.

[theducks]

Originally Posted by ebookscovers

I'm using Sigil to clean up the code in ebook.

Perfect reason. Sigil is about editing CODE , not what the device.

[JSWolf]

Originally Posted by theducks

Perfect reason. Sigil is about editing CODE , not what the device.

But this is about the code for use on a Kindle. Not about how to use Sigil. If I was asking about this same issue using a different editor, I'd still put it in the Kindle Formats forum.

[Hitch]

Originally Posted by ebookscovers

still the same issue when I put in code. Kindle previewer still pushes line up above the superscript. maybe the best thing going forward is to avoid using superscripts and just write 21st as is??

Yes, which is what I mentioned earlier. When it's rendered, the lines will be taller, period.

Just...either switch to bracketed entries, eg. [1], or just live with it. You really can't force a device to NOT leave enough room for the tallest or longest letter, in a font family, after all, now can you? :-)

Hitch