Format Looks Great in Sigil, but not on Device

[rosshalde]

I created a book from scratch today and ran into a snag.

On Sigil:
1) I did all work in code view
2) All looks as it should in preview and book view
3) I used Flight Crew and had no issues
4) I linked the Style sheet and as in #2 all looks fine

BUT... on both Nook and Kobo the CSS seems to be ignored all together. When I tossed the epub into iBook it respected the CSS.
That is not what I am used to. What could I have done wrong in Sigil?

Here is the CSS in case anyone can point out an issue.
p{
text-indent: 5%;
text-align: justify;
font-size: 100%;
}

.s1{
text-indent: 0%;
text-align: center;
font-size: 120%;
font-weight: bold;
}
.s2{
text-align: left;
padding-left: 30%;
text-indent: 0%;
font-size: 85%;
}
.s3{
text-align: justify;
text indent: 0%;
font-style: italic;
font-size: 85%;
}
.s4{
text-indent: 0%;
text-align: center;
font-size: 100%;
}
.s5{
text-indent: 0%;
text-align: center;
font-size: 100%;
font-style: italic;
}
.s6{
text-indent: 0%;
text-align: center;
font-size: 105%;
font-weight: bold;
}
.c1{
font-style: italic;
}

.stanza {
margin-top: 1em;
margin-right: 0;
margin-bottom: 1em;
margin-left: 2em;
text-align: left;
}
.stanza p {
padding-left: 2em;
text-indent: -2em;
}
.image{
text-align: center;
}

body, div, p, h1, h2, h3, h4 { margin: 0; padding: 0; }

[PeterT]

Why not attach either the whole book or a stripped down version of it with one or two chapters... It's far easier for us to look at a complete work than just one fragment of it (the css).

[rosshalde]

Ok,

Here is the book.
It is public domain, so no issue there.
I appreciate the guidance.

[rosshalde]

Also,
it was suggested by some folks on here that as a learning exercise I attempt to code the whole thing myself rather than exporting as an epub file from Pages off a Mac. I took the advice. If anyone sees that I am doing something incorrectly, please let me know so I can do better with the code in the future. I tried to take all the advice from previous posts about using classes.

[PeterT]

One obvious error:

.s3{
text-align: justify;
text indent: 0%;
font-style: italic;
font-size: 85%;
}

Missing hyphen in text-indent

Remember some renderers will ignore the ENTIRE css if there is an error in it...

Also; it's thought inadvisable to have "spaces" within file names in the ePub. Maybe rename items like:
Cover Manual of Prayers.jpg
to
Cover_Manual-of_Prayers.jpg

[rosshalde]

Thank you. That fixed the problem on both devices. I am glad it was something so minor.

I tried to use the tool "Validate with W3C" to check the CSS before I posted originally.
What does that tool do exactly? It didn't seem to do anything.

[PeterT]

When I used the tool it brought up a web page which showed an error in the CSS

[rosshalde]

Any idea of that tool is not part of Sigil for Mac? I can't seem to get it to do anything at all.
I will look into changing the names of the files to eliminate spaces.
I haven't run into any problems as of yet with the spaces, what is the issue with them?

[rosshalde]

I did put the file in calibre after you found the issue and it found the same error. I can do that from now on, but if I can get the "Validate with W3C" to work on my Mac that would be even better

[Mark Nord]

IIRC this feature it is also not working in the windows version of Sigil for a long time now.
So I simply use the direct link to the validator:
http://jigsaw.w3.org/css-validator/#validate_by_input
and copy in my css manually.
Remember to set the validator to check against CSS2.0 oder 2.1
HTH

[Doitsu]

Originally Posted by rosshalde

On Sigil:
1) I did all work in code view
2) All looks as it should in preview and book view
3) I used Flight Crew and had no issues
4) I linked the Style sheet and as in #2 all looks fine

Note that FlightCrew does not check for stylesheet issues, ePubCheck does and found the issue in line 21 of the stylesheet.

<shameless plug>You can also use my Sigil epubcheck plugin, which I had to update because of your file, because I didn't anticipate CSS error messages without line positions.</shameless plug>

(Even though FlighCrew and ePubCheck will often report exactly the same issues, I'd recommend running both.)

[DiapDealer]

Originally Posted by Mark Nord

IIRC this feature it is also not working in the windows version of Sigil for a long time now.
So I simply use the direct link to the validator:
http://jigsaw.w3.org/css-validator/#validate_by_input
and copy in my css manually.
Remember to set the validator to check against CSS2.0 oder 2.1
HTH

Huh? Sigil's W3C css validation works fine with my various Windows environments. This is the first I've heard of anyone having trouble with it.

[Doitsu]

Originally Posted by DiapDealer

Huh? Sigil's W3C css validation works fine with my various Windows environments. This is the first I've heard of anyone having trouble with it.

This might be a file association problem.

I had problems with the Linux version in the past: css files were automatically opened with Geany (a text editor) instead of the web browser. Uninstalling and re-installing Geany fixed the problem.

@Mark Nord: If the css file opens with a text editor, when you select Validate with W3C, uninstalling and reinstalling the text editor might help. If selecting Validate with W3C doesn't open an editor, changing or deleting the open with file association for .css files might help.

[rosshalde]

If selecting Validate with W3C doesn't open an editor, changing or deleting the open with file association for .css files might help.

Currently, when I click on Validate with W3C it does absolutely nothing at all. Nothing opens and it dead. Is anyone able to currently use this tool on a Mac?

I did copy my CSS to the various links that people provided here and it found the error right away.

I realize flight crew doesn't check the CSS...That is why I was pretty sure the issue was in the CSS rather than in one of the files.

[Doitsu]

Originally Posted by rosshalde

Currently, when I click on Validate with W3C it does absolutely nothing at all.

If you double-click a .css file, does it automatically open with TextWrangler, BBEdit or another OSX text editor?

If so you might have to change this file association.

Since both KevinH and user_none use Macs, they can probably give you more specific pointers.