Finding Naked Text in HML

[Thasaidon]

Is there a way of easily finding naked text (i.e. text not enclosed in tags) in Sigil?

F7 Well Formed HTML does not appear to flag them up.

Sometimes when I get rid of a load of "divs" I end up with some naked text.

I am currently switching to Calibre Editor which can easily find them and put basic "<p>" tags around each occurrence.

[DNSB]

Originally Posted by Thasaidon

Is there a way of easily finding naked text (i.e. text not enclosed in tags) in Sigil?

F7 Well Formed HTML does not appear to flag them up.

AFAIR, either Flightcrew or ePubcheck will detect that error though the error message will refer to the next line -- in the sample below the error will show on the third line not the second line.

<p> </p>
this is an unenclosed line!
<p>This is an enclosed line!</p>
<p> </p>

I have both installed and assign plugins 1 and 2.

[DiapDealer]

EPUB2
Flightcrew: "Error schema not satisfied : no character data is allowed by content model near column 1"

EpubCheck: Col: 1: ERROR(RSC-005): Error while parsing file 'text not allowed here; expected the element end-tag or element "address", "blockquote", "del", "div", "dl", "h1", "h2", "h3", "h4", "h5", "h6", "hr", "ins", "noscript", "ns:svg", "ol", "p", "pre", "script", "table" or "ul" (with xmlns:ns="http://www.w3.org/2000/svg")'.

EPUB3
Flightcrew: doesn't work
EpubCheck: doesn't care

I'm assuming since Epubcheck doesn't seem to flag it, that naked text allowable in EPUB3/HTML5.

I'm going to take the opportunity to remind everyone that Sigil's Well-Formed Check is not to be considered any kind of specification validation. As its name implies, it merely checks to see that html is, in fact, parseable. Parseable meaning that tags are all closed and none are improperly nested. Nothing more. It will not catch html/css/xml/epub specification warnings/errors. That is what the validation plugins are for. The Well Formed Check is a quick and dirty "can-I-do-some-automated-processing-on-this-code-without-worrying-about-doing-any-further-syntactical-damage" kind of thing.

[DiapDealer]

By the way, it sounds like a plugin to find and wrap naked text might be in order, for anyone who might be looking for a project to work on.

[Thasaidon]

Originally Posted by DiapDealer

EPUB2
Flightcrew: I'm going to take the opportunity to remind everyone that Sigil's Well-Formed Check is not to be considered any kind of specification validation. As its name implies, it merely checks to see that html is, in fact, parseable. Parseable meaning that tags are all closed and none are improperly nested. Nothing more. It will not catch html/css/xml/epub specification warnings/errors. That is what the validation plugins are for. The Well Formed Check is a quick and dirty "can-I-do-some-automated-processing-on-this-code-without-worrying-about-doing-any-further-syntactical-damage" kind of thing.

AH! I did not understand or had forgotten this. I installed the plugin a looong time ago. Thanks for the information, it makes some things clear now.

[Thasaidon]

Originally Posted by DNSB

AFAIR, either Flightcrew or ePubcheck will detect that error though the error message will refer to the next line -- in the sample below the error will show on the third line not the second line.

<p>*</p>
this is an unenclosed line!
<p>This is an enclosed line!</p>
<p>*</p>

I have both installed and assign plugins 1 and 2.

For the information. I will give them both a try.

[AlanHK]

You can put something in the CSS to make everything else disappear, e.g.

e.g. add color:white; or font-size:0; to your p tag.

Now all p tags will be invisible, leaving you with the untagged text (as well as h1, etc. tags and others, you can white them out too if you have a lot). So quickly scan through the book to find them.

[Thasaidon]

Originally Posted by AlanHK

You can put something in the CSS to make everything else disappear, e.g.

e.g. add color:white; or font-size:0; to your p tag.

Now all p tags will be invisible, leaving you with the untagged text (as well as h1, etc. tags and others, you can white them out too if you have a lot). So quickly scan through the book to find them.

Clever. That is another option.

[AlanHK]

Improved version:
paste this:
p,div,h1,h2,h3,h4,blockquote,li {font-size:0;}
at bottom of CSS file, will override any of your definitions.
Size 0 means you see the whole file on one screen.