Doesn't Like Its Own Strikethroughs?

[daveconifer]

Sorry, got another one.

I have a section of text with character strikethroughs. Rather than copy it, I retyped it in the Book View mode. Then, I used the Format/Strikethrough from the menus above to strike out some words.

In code view this wrapped <strike> and </strike> tags around the crossed out word, as expected. It looks like this: <strike>Ordered</strike>

But when I validate, I get these errors:

1) No declaration for element 'strike'

2) element 'strike' is not allowed for content model '(a|br|span|bdo|map|object||img|svg|tt|i|b|big|sma ll|em|strong|dfn|code|q|samp|kbd|var|cite|abbr|acr onym|sub|sup|input|select|textarea|label|button|in s|del|script)'

Shouldn't Sigil be okay with editing that I did in the Book View mode?


I knew this would be my biggest challenge. Basically, it's a chapter that is a document marked up to look like it was edited (with strikethroughs).

[daveconifer]

I should add that when I view it using Adobe Digital Editions, it looks perfect. But I doubt that Google Play will let me upload it with all those error messages.

[theducks]

<strike> is not on my cheatsheet or at HTML Dog

the CSS way is

text-decoration: line-through;

[Doitsu]

This is indeed a bug. However, you can easily fix this by adding a custom style and a custom clip:

1. Select the main stylesheet and add the following code:

span.strike {
    text-decoration: line-through;
}

(If you haven't created a stylesheet yet, create a new one and link it to the .html files)

2. Press CTRL+ALT+C (or select Clip Editor... from from the Tools menu)

a) Click Add Entry and paste or enter Strike into the Name field.
b) Paste <span class="strike">\1</span> into the Text field. (You might have to double-click the Text field to edit it.)
c) Click Save and Close.

If you've folĺowed these instructions correctly, you should be able to apply your new custom Strike style to selected text by right-clicking the selected text in Code View mode and selecting Clips > Strike from the context menu.

If the span was correctly inserted in Code View mode, but you don't see strikethrough text in Book View mode, you'll need to link the stylesheet to the .html file via the Link Stylesheets context menu in the Book Browser.

[daveconifer]

Thanks, people. I'll try!

[daveconifer]

Ugh, I barely know what a style sheet is and I don't know how to create one.

Wait, I think I've created one.

[daveconifer]

I created the style sheet, but it appears that I have to link it. I'll try to figure out how to do that myself and then carry on with your instructions. Thanks!

[theducks]

stylesheets can be almost brain-dead simple:

p {margin: .5em 0 0 0;
text-indent: 1.2em;
}
span.strike {text-decoration: line-through; }

To OMG specifying everything

.scenebreaker {
border-bottom: 0;
  border-top: 0;
  display: block;
font-size: 1.5em;
font-weight: bold;
word-spacing: 1.5em;
margin-bottom: 1em;
margin-left: 0;
margin-right: 0;
margin-top: 1em;
padding-bottom: 0;
padding-top: 0;
text-align: center;
}

[Toxaris]

If I may give you a good tip... Brush up on basic HTML and CSS skills. That will help you to a large extent... There are some good guides out there. One is on this forum by Pablo (aimed for e-books) and I believe it is also published on the mobileread wiki.

In this case <strike></strike> or <s></s> is deprecated and might not be supported on the readers. To be fair, I haven't come across a reader that did not support it though.

Layout and styling should be done as much as possible via stylesheets. That will make your book smaller in size, easier to maintain and better performing.

[daveconifer]

Thanks, everybody. I learned so much from you.

After slogging through four books, with six to go, I'm intrigued by this style sheet concept and will definitely be digging into it (and will try to get better at .html in general)...

[signum]

Search and replace strike> with del>. Strike has been deprecated and del takes its place. Also, the meaning of "s" has been subtly redefined.