Search results with bulk highlights

[mrprobert]

Delete

[DiapDealer]

I don't quite follow how having them all highlighted at once would help reduce errors in your manual process.

As far as a wildcard string goes: that's what regex is for. Once you have the regex that will match all that you want to fix, you replace and find next until you're done.

This is just a wild guess, but are you trying to make Sigil's Find & Replace feature duplicate the behavior of another favorite text editor? If so, just use the Open With feature and use that favorite editor.

[mrprobert]

Originally Posted by DiapDealer

I don't quite follow how having them all highlighted at once would help reduce errors in your manual process.

As far as a wildcard string goes: that's what regex is for. Once you have the regex that will match all that you want to fix, you replace and find next until you're done.

This is just a wild guess, but are you trying to make Sigil's Find & Replace feature duplicate the behavior of another favorite text editor? If so, just use the Open With feature and use that favorite editor.

I have no editor in mind and I have no problems using a regex search (DFA, anyone?). It's my old eyes that is the problem. With verbose code, a visual cue from seeing the matches before and after the current selection make it easier for me to see what needs to be changed. For my specific use the errors are proximate to each other and it helps if I can see all the matches in view.

Im my earlier post I think I have mixed up book browser and code view. I get dizzy swiveling my head between looking at the headings in the preview window and in the nav, and trying to sort out the various IDs and their proper order.

It may be that the particular complexity of this project is fairly rare and I should just figure it out.

Thanks.

[KevinH]

I have an epub with dozens of errors of type 'link target is before the previous link’s target in document order.'

Typically this is an NCX or Nav issue where spine order and the order used n the nav/ncx is inconsistent. It can be as simple as having one link out of order.

The solution is just to rebuild the TOC from the original h1-h3 tags if possible. Ids themselves are not numbered but in the nav and ncx the order must match the playorder, (typically the same as the spine order of the files).

In fact the playorder attributes are not needed anymore.