FlightCrew Error in Sigil

[oenopion]

Okay, two things.

First, I was trying to add a second paragraph style to an ebook that would allow the bulk (a novel) to run under "p style" with an indented paragraph, except for a "p.first" to start every chapter. I've formatted multiple books this way, without issue.

But, I wanted to add an interview in the back matter and format it typical to interviews, all with no indent, and a space between paragraphs. I created a p1 style for this, which worked fine, except for the &nbsp between paragraphs. For whatever reason, the p1 when applied, messed with the space between paragraphs and created one long paragraph out of everything.

As a work around, the &nbsp would work if I wrapped it in a regular p style, and with find/replace it seemed an easy fix. Until FlightCrew, which turned up the "Error schema not satisfied: no declaration found for element 'p1' near column 5' which corresponds to the start of every p1 paragraph.

Is there something I need to add to the style? And would that fix the &nbsp issue? I did try to increase the bottom margin in the p1 style but it didn't seem to register and do anything.

Also, the ebooks (both epub and mobi) are displaying fine, but I'd like to wipe the error code off the board, and fix the &nbsp as well.

[Notjohn]

Definitely the spacing should be handled by margin-top and margin-bottom. For example:

p.interview {
margin-top:0.5em;
margin-bottom:0.5em;
text-indent:0em;
text-align:justify;
}

In the text, <p class="interview">

If half a line isn't enough at beginning and end of the interview, you could create a interviewfirst class for the first para, with a 1 em top and bottom margin. Subsequent paragraphs would be 0 top and 1 em bottom.

[Doitsu]

Originally Posted by oenopion

[...] Until FlightCrew, which turned up the "Error schema not satisfied: no declaration found for element 'p1' near column 5' which corresponds to the start of every p1 paragraph.

That message is usually displayed for non-standard HTML tags. You most likely used something like:

<p1>Lorem ipsum</p1>

BTW, FlightCrew is outdated. You might want to check your book with the IDPF Validator.

Originally Posted by oenopion

And would that fix the &nbsp issue? I did try to increase the bottom margin in the p1 style but it didn't seem to register and do anything.

Your problem description is too vague. Please post the relevant HTML/CSS sections and screenshots that illustrate your problem.

[JSWolf]

You'd be best off to install the epubcheck plugin for Sigil sand use epubcheck 4.0.2.

https://www.mobileread.com/forums/sh...d.php?t=248186

[PeterT]

Why not use a different style sheet for the interview in the back matter?

[oenopion]

Awesome! Thanks Notjohn for the code, worked like a charm. As Doitsu pointed out I did use the p1 like in his example. I was told it could work, but by someone who doesn't do ebooks. Now I know what to do.

Ran the book through IDPF Validator with no errors. And with FlightCrew being outdated, should I use the EpubCheck plugin instead? Or is the browser version enough?

[oenopion]

JSWolf, I was typing while you commented, so you read my mind. Thanks for the link, will check out the plugin.
PeterT, good idea. I'm new to anything beyond the stuff I have figured out, and hadn't thought of that. But it would probably be good practice to just link a new style sheet to any new formats like that.

Thanks again, everyone!

[HarryT]

Originally Posted by oenopion

Awesome! Thanks Notjohn for the code, worked like a charm. As Doitsu pointed out I did use the p1 like in his example. I was told it could work, but by someone who doesn't do ebooks. Now I know what to do.

No, you can't invent your own tags; all you can do is specify a style for the existing ones.

[Turtle91]

Originally Posted by PeterT

Why not use a different style sheet for the interview in the back matter?

I find adding additional sheets can get confusing...especially if they are all named style1, style2, style3, etc. Which style sheet goes with which html file???

I prefer to keep everything on a single sheet. That makes sure there is consistency in the style naming conventions. It is very frustrating when I see <p class="somestyle4"> used on one html file, then the same style name is used on another html file to do something completely different.

BUT, I agree with the idea that you can simply create a new "section" of defined styles on the same style sheet. I use the <div> tag to define when there is a large number of lines affected. It keeps the code very clean and easily readable. Plus, the nature of CSS hierarchies ensures that the more specifically defined div elements will have the correct styling.

For example:

Instead of:
p.interview {margin:0.5em 0; text-indent:0; text-align:left}

<p class="interview">Some question</p>
<p class="interview">Some answer</p>
<p class="interview">Some question</p>
<p class="interview">Some answer</p>
<p class="interview">Some question</p>
<p class="interview">Some answer</p>
<p class="interview">Some question</p>
<p class="interview">Some answer</p>
...

I would use:
div.interview p {margin:0.5em 0; text-indent:0; text-align:left}

<div class="interview">
     <p>Some question</p>
     <p>Some answer</p>
     <p>Some question</p>
     <p>Some answer</p>
     <p>Some question</p>
     <p>Some answer</p>
     ...
</div>

In Sigil I set a "clip" that will automatically surround any text I have highlighted with the <div class="">...</div> tags at the click of a button. It is then very simple to add the class name for the particular style I want on those highlighted lines.

FWIW,