Superscript widow's

Themus · 10-01-2012, 07:37 PM

I have some superscript's that are dangling by themselves rather than staying with the sentence they are to be connected to; Can a person "tie" them to the beginning of the sentence where they belong.

Ie. is there such a thing as a non-breaking space or superscript? I found out tonight how to resize them in sigil from Calibre so that they don't cause the lines to lack even spacing. They look good and not very conspicious. But I have some where they fall at the end of the sentence, rather than with the next sentence where it belong.

As always, thank you for your time.
This is an art.

mrmikel · 10-01-2012, 08:35 PM

There are non-breaking spaces, see: http://www.w3schools.com.

But non breaking means non breaking, which means you could end up with very short sentences if someone decides to increase the print size.

I generally don't use super or sub script because if it is small enough to not affect the line spacing you can't read it. [1] are used by some people instead, though they are not as pretty. But if you have to do lots of footnotes, then it is not going to be too pretty anyway. You might use italics if they are not used otherwise in the text.

Jellby · 10-02-2012, 06:17 AM

You can always wrap the word and superscript in a <span> with "whitespace: nowrap", but I believe that's adding clutter to work around a problem of some specific renderer (which shouldn't be inserting a linebreak at a subscript or supescript).

However (from the CSS spec):
Note. CSS 2.1 does not fully define where line breaking opportunities occur. Floated and absolutely-positioned elements do not introduce a line breaking opportunity.

This means that the renderer is not going against the spec (just against common sense), so using the span might be justified. Anyway, I wouldn't do that, I'd complain to the vendor/developer instead.

10-01-2012, 07:37 PM	#1
Themus Zealot Posts: 133 Karma: 998 Join Date: Apr 2010 Device: Nook	Superscript widow's I have some superscript's that are dangling by themselves rather than staying with the sentence they are to be connected to; Can a person "tie" them to the beginning of the sentence where they belong. Ie. is there such a thing as a non-breaking space or superscript? I found out tonight how to resize them in sigil from Calibre so that they don't cause the lines to lack even spacing. They look good and not very conspicious. But I have some where they fall at the end of the sentence, rather than with the next sentence where it belong. As always, thank you for your time. This is an art.

Similar Threads
Thread	Thread Starter	Forum	Replies	Last Post
Superscript best practices?	DiapDealer	ePub	19	04-14-2012 04:28 PM
Black Widow - Gotthelf ?	carpetmojo	Reading Recommendations	3	12-28-2011 12:02 PM
html/ePub to mobi superscript problem	DarkElf	Conversion	1	08-23-2011 11:18 AM
Superscript and Subscript	ramjet1953	Sigil	1	06-13-2010 07:15 AM
Superscript in titles	paulpeer	Sigil	5	01-20-2010 08:37 AM

10-01-2012, 08:35 PM	#2
mrmikel Color me gone Posts: 2,089 Karma: 1445295 Join Date: Apr 2008 Location: Central Oregon Coast Device: PRS-300	There are non-breaking spaces, see: http://www.w3schools.com. But non breaking means non breaking, which means you could end up with very short sentences if someone decides to increase the print size. I generally don't use super or sub script because if it is small enough to not affect the line spacing you can't read it. [1] are used by some people instead, though they are not as pretty. But if you have to do lots of footnotes, then it is not going to be too pretty anyway. You might use italics if they are not used otherwise in the text.

10-02-2012, 06:17 AM	#3
Jellby frumious Bandersnatch Posts: 7,543 Karma: 19001583 Join Date: Jan 2008 Location: Spaniard in Sweden Device: Cybook Orizon, Kobo Aura	You can always wrap the word and superscript in a <span> with "whitespace: nowrap", but I believe that's adding clutter to work around a problem of some specific renderer (which shouldn't be inserting a linebreak at a subscript or supescript). However (from the CSS spec): Note. CSS 2.1 does not fully define where line breaking opportunities occur. Floated and absolutely-positioned elements do not introduce a line breaking opportunity. This means that the renderer is not going against the spec (just against common sense), so using the span might be justified. Anyway, I wouldn't do that, I'd complain to the vendor/developer instead.