Does ‘Keyboard Maestro’ (with all the text) compile cleanly if it is the only document compiled?
Does ‘Keyboard Maestro’ compile cleanly if you compile the whole project but leave out the screenshot page that follows ‘Keyboard Maestro’?
Will the project compile okay to a different format, such as RTF or Word?
When you first compile and get the heading on one page and the text on another, we see down to section 4 in the PDF. What happens to section 5? Just disappears? Or is it on the next page after the screenshot?
So it will compile with all the text and the right spacing after the heading to RTF (even if it looks less than lovely), but the break happens after the heading if you compile to PDF. Very curious.
The inspector on your video link suggests the project dates back a few years. I’m not at a Mac now, but there is a setting in, I think, Edit … Text Tidying … Zap Gremlins, which is supposed to zap any odd characters that might have crept into a document. It might be worth trying that (you can always backup the file before you use the command).
If you duplicate the project and then delete all the other files so that only the two KM files are left, do they compile okay to PDF?
If they do, add back in one of the files above and below the KM files and see if they break the compile. If they don’t compile, would you be happy to share those two pages on the forum or by PM as a standalone project? Would be happy to see if I could get them to work, or perhaps another forum member could.
Alternatively, as the issue appears to be very specific, I imagine you might need to get in touch with tech support and ask them to look at the file for you. I tried to replicate the settings from your video, but I didn’t run into the same problem.
Text Tidying - I’ve tried this, it didn’t seem to affect anything.
I’ve actually just created an entirely new project and copy-pasted sections over. I am still encountering the error on the long section, where it adds a page break and then cuts off the end.
Those files aren’t Scrivener projects so we can’t open them. (In fact they’re just one of the xml files within the projects – behind the scenes Project.scriv files are actually folders (bundles) containing hundreds of separate files. We need to see the entire project.)
The best way for us to look at them is to zip the .scriv files up in the Finder (right click on the project and ‘Compress’ them), then attach them to a post here. To do that click on the three lines next to the Options button below and choose Attachments, then Add Files.
All your documents are actually in tables (the borders are invisible, which is why it’s not obvious. To see this, go to the Keyboard Maestro document and make sure View > Text Editing > Show Invisibles is ticked. You’ll see a blue border round the entire text. That’s why compile is having problems – it’s trying to fit one long cell on a page and it can’t.
