problem with added characters

[Oldpilot]

In my html file, I have the following line:

<span class="underline">action</span> and <span class="underline">decision</span>

But when I open the html file in Sigil, I see this:

<span class="underline&gt;action&lt;/span&gt; and &lt;span class=" underline="">decision</span>

As a result, epub validator makes this complaint:

attribute "underline" not allowed here; expected attribute "dir", "id", "style", "title" or "xml:lang"

So, two questions:

1. Why do you suppose Sigil makes such radical changes in the text, accepting some instances of < and > but changing others, and again adding a space and a straight quote which seem to have created invalid epub?

2. Am I correct in thinking that epub validator is complaining about the space and the apparent extra " in the second instance, to wit: " underline="">

There are many instances of span="underline" in the document, but only three errors relating to the word "underline".

Thanks!

[theducks]

Originally Posted by Oldpilot

In my html file, I have the following line:

<span class="underline">action</span> and <span class="underline">decision</span>

But when I open the html file in Sigil, I see this:

<span class="underline&gt;action&lt;/span&gt; and &lt;span class=" underline="">decision</span>

As a result, epub validator makes this complaint:

attribute "underline" not allowed here; expected attribute "dir", "id", "style", "title" or "xml:lang"

So, two questions:

1. Why do you suppose Sigil makes such radical changes in the text, accepting some instances of < and > but changing others, and again adding a space and a straight quote which seem to have created invalid epub?

2. Am I correct in thinking that epub validator is complaining about the space and the apparent extra " in the second instance, to wit: " underline="">

There are many instances of span="underline" in the document, but only three errors relating to the word "underline".

Thanks!

In all cases I have seen Tags changed to entities, there has been something malformed in the Tag pair and it got treated as/converted to text.

In this case, I think it is the uppercase-bracketed [B]

You would be best served using the newer way of doing bold, using a selector <p class="bold">... </p>
and in the CSS
.bold { font-weight: bold; }

[mmat1]

Originally Posted by Oldpilot

1. Why do you suppose Sigil makes such radical changes in the text, accepting some instances of < and > but changing others, and again adding a space and a straight quote which seem to have created invalid epub?

2. Am I correct in thinking that epub validator is complaining about the space and the apparent extra " in the second instance, to wit: " underline="">

1. You probably missed the Quote between the first underline and the >

2. Epub-Validator takes the second underline as attribute-name, not as value and probably does not see the missing quote before the second underline. Don't think too much about it...

[Oldpilot]

You would be best served using the newer way of doing bold,

But there is no bold in that set of underlinings! Are you saying that span class=underline should be p class="underline"? I should use paragraph tags within a sentence? Surely that will create a new line?

And

You probably missed the Quote between the first underline and the >

I don't see any missing quote. It reads: <span class="underline">. That's pasted from the original html file.

Perhaps I should have said that the html validates without a problem.

I suppose I could simply use italics, though that's not true to the original.

[theducks]

Originally Posted by Oldpilot

You would be best served using the newer way of doing bold,

But there is no bold in that set of underlinings! Are you saying that span class=underline should be p class="underline"? I should use paragraph tags within a sentence? Surely that will create a new line?

And

You probably missed the Quote between the first underline and the >

I don't see any missing quote. It reads: <span class="underline">. That's pasted from the original html file.

Perhaps I should have said that the html validates without a problem.

I suppose I could simply use italics, though that's not true to the original.

I went back and corrected my post almost as soon as I posted , just not enough

[theducks]

All I can think of: there was a mismatch in the closing </span> or different quote marks were used. something unbalanced the span

[DiapDealer]

I've never seen Sigil turn a opening/closing tag into an entity on well-formed (x)html. I'm not saying yours isn't/wasn't well-formed ... I'm just saying that out of the 100 of thousands of lines of (x)html code I've run into/through Sigil ... every single instance of &gt; or &lt; has been my fault. 100%. Either I purposely entered the entities because I wanted them there, or I screwed up the code and Sigil failed to correctly guess what I did wrong.

I've tried importing, pasting, opening that line of html you posted and I just can't get Sigil to screw it up. The only way I can get Sigil to reproduce your problem is by forgetting one of the attribute quotes.

[Jellby]

Maybe some of the quotes are curly/directional (“”) instead of straight? Delete and write them again and see if that helps.

[ghostyjack]

I've had this happen to me a couple of times with the 0.6.0 beta's. I never could figure out what caused it as looking at my master copies of the files that had this, they looks perfectly fine. Certainly the quotes were all straight.

This seemed to be a random occurance, I could never replicate it. It just seemed to happen.

[mmat1]

Originally Posted by Oldpilot

You probably missed the Quote between the first underline and the >

I don't see any missing quote. It reads: <span class="underline">. That's pasted from the original html file.

Sorry, but: There is no error now in your posting, but the error was there when you pasted it to your epub (or the quote was accidentally deleted afterwards).

Just try it out: turn well-fornmed check off, paste your code to a blank xhtml, remove that quote, save and close the file and open it again and look what sigil did with your code.

[Oldpilot]

The problem seems to have been my using underline when I should have used u. The file now validates.

I shouldn't have confused the matter by asking about the messed-up characters. Sorry!

[theducks]

Originally Posted by Oldpilot

The problem seems to have been my using underline when I should have used u. The file now validates.

I shouldn't have confused the matter by asking about the messed-up characters. Sorry!

<span class="underline">

should not cause a validation problem.
I would expect that there would be a (at minimum):

.underline { text-decoration: underline; }

in the CSS, but Flightcrew does not fail a missing CSS selector