![]() ![]() So I’ve been writing in Scrivener using Stage Play format (tweaked by me) thinking “Then I’ll change it all into Screenplay format so that MM Screenwriter or Highland or Fade In Pro understands it, then once it’s all safely exported, I’ll change it all back in the new application.” But nothing else understands stage play format. The reason it’s important is this: I’m writing a stage play. I’d have to dig a lot further and I’m on deadline. I’ve trashed every prefs file, reinstalled Scrivener from a fresh download, and it’s still bust. Sometimes – occasionally – I get the substitutions box, set that all up, say “OK”, and… nothing happens. Sometimes it gives me a warning that I’m overwriting a document-specific format, and I say “OK” and nothing happens. ![]() Sometimes I change the Format and nothing happens. ![]() (“Scene Direction” = “Action”, for example) and then applied the changes to ALL the documents. Around v2, I think, if you changed the Script Format a little box popped up asking you what in the new format was equivalent to what in the existing one. Then, by the grace of God – or the grace of Keith I get them mixed up sometimes – things changed. (I even recall reading dire warnings in TFM that you’d better sort out your format before you started writing, because once you throttled up and released the brakes, you were committed.) Existing documents in Script Mode stayed as they were. That’s to say, if you changed the prevailing Script Format – say from Stage Play to Screenplay – only NEW documents would take on the new format. I remember (I think) that originally changes to Script Format were non-retrospective. I haven’t seen anything about this on the fora, so this is by way of a preliminary RFC to see if it’s just me. (Scrivener 2.3.1/ OS X 10.8) <- What by the Flesh of the Prophet that damned smiley is doing there, I have no idea. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |