If you’re exporting to an application that has really powerful search and replace features, such as InDesign CS3 and 4, you might try the trick I use. As I write in Scrivener, I tag text with the quote marks some European languages use. To almost every application around today, they’re just text and, unlike the underline/MultiMarkdown scheme (which depends for its meaning on which side of the letter the underline is on), they are unambiguous tags. They also let me tag text with what will become character styles rather than just the Word rtf formatting for italic in a specific font. Word formatting imported into InDesign causes all sorts of woes, so whenever possible I import text devoid of all formatting.
My scheme uses these tags:
(I’m still trying to come up with a way to tag smallcaps.)
I’ve got some GREP search and replace scripts inside InDesign that let me replace those markers with the appropriate character style. The only thing I must remember is to run the scripts in the proper order from Bold Italic to Italic.
This is also a handy trick to do something that stock InDesign can’t do, place italics and bold inside an index. Just include the tags inside an index definition and convert them after the index is generated.
For what it is worth, I’ve been encouraging Adobe to include the very simple paragraph styling scheme that PageMaker had. Any paragraph that begins with text inside angle brackets gets placed inside a paragraph with that name as its paragraph style. It’d make it much easier for writers who use applications like Scrivener to tell publishers, who may use InDesign, how a book is formatted.
For instance, in Scrivener this text:
This is a paragraph that is indented like quotes should be.
would come into InDesign without the text inside the angle brackets but with a Quote paragraph style assigned. InDesign can already do that sort of thing, but only if you also do some other and more complex formatting. Programmers like that sort of stuff. Most writers don’t.
For writers, this would mean that they’d be able to specify for their publishers inside Scrivener which paragraphs are first-level headers, second-level headers or quotes. That’s something that’s easily lost in the primitive sort of rtf that OS X understands. And it would avoid mistakes that are often hard to spot.
If you use any Adobe product and have ideas you’d like to see in future products, go to:
You might even suggest the PageMaker idea above. It’s already in their idea list, it just needs more user support.
The equivalent webpage for Apple is here:
You might suggest that Apple add GREP to the features of Cocoa Text, so it can be included inside Scrivener. What is GREP? It’s search and replace done right and bears the same relationship to regular S&R that a Porsche race car does to a Model T Ford.
–Michael W. Perry, Seattle