The FindChangeList script takes some getting used to, I personally prefer Multi-Find/Change 2.0 and would post a link if it didn’t appear that their site was down. But FindChangeList uses a little different GREP than InDesign’s Find/Change dialog. First you have to remember to double escape everything (ie periods, you have to do . not just \.), I played with them and at least got one working (it’s a little modified from what you had (using Keep (\K) as a positive look-behind which is zero-length so you dont have to worry about using a capture group number or $0 in the changeTo field.), still working/playing on the others.

grep {findWhat:"wK-"} {changeTo:"~-"} {includeFootnotes:false, includeMasterPages:false, includeHiddenLayers:false, wholeWord:false}

Aaron

Hey Chris,

I’m a little confused, are you using the Split Document option for the Chapter title or whatever starts each chapter and you’re getting this issue? or are you applying the Split Document option for the endnotes? or for a paragraph style after a footnote? I only ask because your post sounds like you are applying it to footnotes. And are you using the Split Document option on styles within your chapter/section? I would advise against that as InDesign will view that as the end of the chapter/section and all the footnotes/endnotes will be placed at the end of each (you are basically telling InDesign to create a new HTML page every time you use Split Document and theoretically each chapter should be in one HTML page not multiple, if you’re doing coding after export, you can get around this but its a lot easier just to do it in InDesign) and really unless you have an image you want to force to another page, I would advise against using the Split Document option on any style other than the first style at the start of each chapter (usually the chapter number or title).

You don’t need to abandon your endnotes, that’s actually rather normal, unless you are taking advantage of the popup notes in iBooks, endnotes are really the only way to do footnotes.

Hopefully that made sense, let me know if you have more questions,

Aaron

David is on the right track, I would do it a little differently with a positive lookbehind or a Keep (\K) to look for (but not capture) the punctuation and space before, such as:

(?<=\. ).+?\?
or
\. \K.+?\?

they both do the same thing, just in a different way. They both look for a period space (both zero width so as not to be included or affected in your replace) on one end and a question mark on the other end, and, of course, everything in between.

you can either then group the .+? like (.+?) as a capture group or if you can just use it as is and in your replace field use $0 which basically matches everything that was found.

Let me know if you have any questions.

Aaron

Frank,

The issues you have brought up have to do with the different specs for different eReaders. They all kinda have their own way of doing things and you kinda have to find a happy medium. I would say try stripping your CSS down and try to be as minimal as possible. (https://ebookarchitects.com/blog/why-ebook-conversion-is-complicated/)

For tables for example are you setting the border to “collapse”?

As far as hyperlinks, are you referring to the TOC? or is this all the URL hyperlinks as well? I havent personally run across this, but I have had times when I’ve exported and all the TOC links are the same link.

Aaron

Blusse, I have put together a sample TOC with a few levels of nesting with some light commenting to try and explain it. Its pretty much a complete toc.xhtml, I have included a Page List nav section which you can delete, its just an example of how a Page List would look in the toc.xhtml.

https://www.dropbox.com/s/fvvuluolsx9wfss/toc.xhtml?dl=0

Hey Robert,

Is the this one INDD file that includes everytying or did you make multiple (one file per chapter/frontmatter/glossary item) and combine them into an InDesign book file (INDB )?

Aaron

Hey Gregory,

From the errors you listed it seems like the issue is with the automatically created TOC anchors, I think these are added when you create the TOC, and I believe have to do with the “Create PDF Bookmark” or “Make text anchor in source paragraph” checkboxes, not sure which one exactily. I might delete the TOC, in the Hyperlinks window in the dropdown menu select “Delete unused hyperlinks” and then regenerate your TOC. I think what happened is a few of them got deleted and epubcheck is freaking out because you have a link to anchors in the TOC that are missing in the text so they are basically pointing to no where.

Maybe make a copy of the file and try it, just to be sure. I’ve done this a few times, for different reasons (mainly to get rid of the links because I do a lot of back end HTML work after export) but I think getting rid of all the links and then regenerating the TOC so that it readds them should take care of your linking errors.

Aaron