Index Creator bug maybe?

[Siggy15]

This is processed correctly:

<span class="sigil_index_marker" title="Now we're equally"> </span>

This is ignored:

<span class="sigil_index_marker" title="Now we're equally"></span>

This is also ignored:

<span class="sigil_index_marker" title="Now we're equally"><img src="now.jpg"/></span>

[BetterRed]

Suggest you always put code in code tags, the forum software has a habit of injecting spurious spaces,

<span class="sigil_index_marker" title="Now we're equally"> </span>

In Advanced mode it's the '#' button.

BBCodes supported on MR ==>> https://www.mobileread.com/forums/misc.php?do=bbcode

BR

[KevinH]

The one that is processed correctly has a text node to process (even if it is just a single space), the second and third example have no text node to process. You need a text node so that the QRegularExpression has something to attempt to match.

Not a bug, but a requirement for a text node to process an index entry, and not an img tag or other non-text node.

[Siggy15]

That's pretty much what I concluded. Not really ideal behavior, if the title is supplied then a "text node" should not be required. But the workaround is simple, and I haven't seen a reader app that messes it up, yet. Remember Internet Exploder? Most epub readers are a lot worse, you never know how standard html will be displayed, and that space could be rendered even though it shouldn't, that is my concern.

Sigil preview actually has excellent rendering, with a few buttons added it could be used as a reader, in fact I often read entire books in Sigil already. Previous, Next, and Home, where Home connects to a special tag marking the table of contents page.

I actually use the heck out of Sigil, which is why I have all these annoying little bugs to report.

[KevinH]

Just install the Sigil plugins that actually supply their own e-reader.