white space

[JLius]

Originally Posted by Toxaris

At least some models of the Nook have issues with the shorthand notation. So, it is better to write them out. Ignoring can be one thing, misinterpreting another. Not that bad when the value is 0, but still.

Then why, see your website (mijn standaard stylesheet), do you use the shorthand notation yourself?

[theducks]

Originally Posted by JLius

Then why, see your website (mijn standaard stylesheet), do you use the shorthand notation yourself?

It is a Nook issue, not an ADE issue.
I don't see Nook on either of your lists of personal devices. So if the edits are for personal use...

I tend use the simple short forms, but not the full versions.
eg.

border-width: thin;
border-style:solid;
border-color:  green green green green ;

and not the full short form:

border:thin solid green

(in the cases like border, there can be other reasons that the short form can not be used)

[Toxaris]

Originally Posted by JLius

Then why, see your website (mijn standaard stylesheet), do you use the shorthand notation yourself?

Because I don't use a Nook?

[JLius]

Sure, I get that, but maybe one day you'll decide to buy a nook and then you'll have to change everything? I don't have a nook, but still I'd like my code to work for every device since I might buy one some day, or maybe my wife buys one, or my son, or...

[JSWolf]

Actually, try this...

Take your Word document, save it as a docx format file, run it through Calibre after turning off margin shorthand.

Margin shorthand turning off...
1. Preferences
2. Common options
3. Look and feel
4. Check Expand CSS
5. Apply
6. Close
7. Restart Calibre

[theducks]

Originally Posted by JLius

Sure, I get that, but maybe one day you'll decide to buy a nook and then you'll have to change everything? I don't have a nook, but still I'd like my code to work for every device since I might buy one some day, or maybe my wife buys one, or my son, or...

That is WHY you want to use a stylesheet;

one place to make (workaround) changes.
one place to /* disable */ misbehaving styles. This does assume the device will not barf on a missing style definition

[jimb949]

My paragrafts start with <p class="MsoNormal"> and end with </p>. So should I put those margin codes in my MsoNormal stylesheet or should I make a p stylesheet and put them in there instead?

[theducks]

Originally Posted by jimb949

My paragrafts start with <p class="MsoNormal"> and end with </p>. So should I put those margin codes in my MsoNormal stylesheet or should I make a p stylesheet and put them in there instead?

in msonormal


The class= will override the p attributes

p {color: red;}
p.msoNormal: color:black;}

<p>This will be Red
<p class="msoNormal">This will be black

[Nebucad]

Originally Posted by jimb949

When I check my book on nook there is a blank space between each and every one of my paragraphs and it looks bad.

Hi, i assume it is not a StyleSheet problem because you write

Originally Posted by jimb949

I can delete them one by one but that would take me forever because I have 28 chapters.

So i doubt it a stylesheet setting could help you with your problem at all.

It sounds for me you have problem which could nicely solved by RegEX.

First open your SiGIL-Editor and find the "blank" paragraphs you have to see how they`re entered in the .html File <p> isn't the same like <p class="idk" id="whoknows">!

2nd step
open find-and-replace (usually strg+f) you've to enter 2 thing
Search-Line: <p>\s*</p>
replace-Line: <empty no letter no char, nothing>

IMPORTANT
check the setting, just run it manually and run it once to see what happend
(this setting will erease all TAG (p-TAG) with whitespace between the TAG, this also erease p-TAG's who goes over several lines and have more than 1 whitespace, this order doesn't ereas p-TAG with whitespace and letters between the opening and ending-TAG)

Make sure the annoying paragraph match the <p> paragraph in the Search-line. i.e <p class="idk">\s*</p>

whitespace outside a TAG will be ignored anyway.

[JLius]

Originally Posted by theducks

That is WHY you want to use a stylesheet;

one place to make (workaround) changes.
one place to /* disable */ misbehaving styles. This does assume the device will not barf on a missing style definition

Of course, by changing everything I mean changing your style sheets. But my argument still stands, no? why not make your style sheet acceptable for all devices, as much as you can?

[theducks]

Originally Posted by JLius

Of course, by changing everything I mean changing your style sheets. But my argument still stands, no? why not make your style sheet acceptable for all devices, as much as you can?

Because you have the Apples's and the Nook's and the 40 bazillion models that all do EPUB different

There is no One style to rule them all , except an UGLY one
(plain, basic, one level above plain text )

[Hitch]

Originally Posted by theducks

Because you have the Apples's and the Nook's and the 40 bazillion models that all do EPUB different

There is no One style to rule them all , except an UGLY one
(plain, basic, one level above plain text )

+1 and then some.

Hitch

[JSWolf]

Originally Posted by theducks

Because you have the Apples's and the Nook's and the 40 bazillion models that all do EPUB different

There is no One style to rule them all , except an UGLY one
(plain, basic, one level above plain text )

Let's just ignore iBooks for now.

You can make a CSS that works for most ePub readers and if it doesn't, the software is broken. You just have to take into account no shorthands like margins. Don't try to get fancy. Use an embedded font with a true embedded smallcap font if you use smallcaps. Just do it right and it works.

[Jellby]

Originally Posted by JSWolf

You can make a CSS that works for most ePub readers and if it doesn't, the software is broken.

I agree with that, but then the remarks below are extra. It's perfectly fine (spec-wise) to use shorthand margins and font-variant:small-caps, if they don't work it's the software's fault

You just have to take into account no shorthands like margins. Don't try to get fancy. Use an embedded font with a true embedded smallcap font if you use smallcaps.

[JLius]

Thanks guys, very enlightening!