I’m undecided about whether to use the Twine editor for adding new bits to my branching story, or whether to export three dozen passages to Scrivener, work on the story there, and then import everything back into Twine. That would be a lot of extra work!
Scrivener is a much better word processor, of course. One wouldn’t expect Twine to rival it in that department. But here’s the problem:
I had written this story a few years ago in Scrivener. I recently imported it into Twine as a linear series of passages and then started adding branching bits. What I have now discovered, and it’s deeply disturbing, is that Twine’s text editor types straight quotes and apostrophes, while Scrivener does automatic conversion into curly quotes and apostrophes. Firefox (and probably all other browsers, I haven’t checked) preserves this distinction when displaying the text.
As a result, I now have a Twine story that is internally inconsistent. Some passages use curly quotes, while others use straight quotes. For me, as a professional writer and editor, this is unacceptable. For my own published work, I demand consistency of myself.
I’m sure I can find a way to type curly quotes into the Twine editor using special keystrokes on my PC. It’s extra work, but it’s manageable. Conversely, if I do the writing in Scrivener, then any code (such as in linkreplace) that demands straight quotes is going to require extra handling. If I type it in Scrivener, I’m pretty sure the code will malfunction.
I’m just thinking out loud here – this isn’t exactly a technical question – but I’m curious whether others have encountered the curly quote issue in Twine, and how they may have dealt with it.