![]() To do this:Ģ) Select the Plugins tab and then the Exporters subtab.ģ) Change the plugin for Rich Text Format from "Storyist RTF Exporter" to "OS X Exporter." Montage is probably missing support for these features or does not correctly implement them.įortunately, you can configure Storyist to use the Apple OS X RTF exporter if you want. This is because Text Edit also uses the Apple OS X RTF exporter too (surprise, surprise). Here is what is probably going on: When you open the file in Text Edit and then save it again, Text Edit strips the stylesheet (and header/footer) information. Try opening it in Word, Pages, and Neo Office and you'll the the same result. You mentioned that the Storyist RTF displays correctly in Text Edit. I've reported this to them for "enhancements". So it takes some clean-up, but not a prohibitive amount. Once done, Montage does a vairly good job of recognizing style-tags with one exception: Any Action element other than the first after the Scene heading, is formatted incorrectly as dialogue. I won't argue that, but seems it has to be "cleaned up" by somebody else's "output to rtf" routine before Montage can parse it. This would lead one to assume that Storyist's output rtf is somehow non-standard. Then load it in Montage and it works *perfectly*. Then open it with TextEdit (I use JEdit), save it again rtf. ![]() Relative to exporting script from Storyist to Montage I have figured out how to do it. When imported to Storyist, it tags all text "General". Attached is 1 page MS-rtf output from Montage. It seems the only likely way to converse with Montage.īlabber, if you'd be willing to forward some "Microsoft RTF" from Montage, just a scene or two with some action, character, parenthetical, dialog, and transition elements, I'd be happy to take a look. With fleet fingers an QuickKeys macros I've found relatively rapid ways to convert everything by hand of course I would prefer not to.įor future update consideration of Storyist: add a conversion from. Montage exports both Microsoft RTF as well as Apple RTF, the difference of which I couldn't imagine, but I'm sure Microsoft imagined it quite well. Unfortunately, you'll still have to apply character and parenthetical styles by hand. The Scene Heading style should now be applied to all scene headings. ![]() The defaults should be set to apply Scene Heading to paragraphs that begin with INT, EXT, or I/E. Try this:ġ) Create a new project from the Screenplay template.ģ) Set the style at the cursor to the Action style.Ĥ) Open the text-only file in Text Edit and paste the file into the Storyist Script.ĥ) Choose Format > Style > Apply Styles by Matching Text. Note that if you do import a text file, you can use the style matching tools in Storyist to apply scene headers. Does Montage export Final Draft FCF files? This format is even older than FDR, but Storyist can import it. It looks like Montage only exports Final Draft FDR files (an older but still widely used format), so unfortunately that won't work for you. The Storyist RTF importer (which is not based on the Apple importer) does import stylesheets, but the information needs to be there. This is a shortcoming of Apple's RTF converters, which a number of Mac apps use. I'm guessing that Montage doesn't export stylesheets in their RTF files, which is where the scene header, action, and character name information would be. For my 8-12 pages of test material that's workable.īut if someone were to give me 30 or 40 pages of script for editing, or additional work, this hand-tagging looks like a big thumb-ache! Is that the way it's supposed to work? I've had to go in and tag the style for every scrap of incoming text. Unfortunately none of the formatting is identified in Storyist as scene headers, action, character name, parenthetic instruction or dialogue. So now I attempt to import txt and rtf files produced by Montage. I have a sent a note to Mariner's support crew for their oddity: All text I produce in output (txt or rtf are the only viable options) from Storyist is imported there upper case! I've verified that the output from Storyist is not muddled in this way it does indeed happen during Montage's import. My difficulty has come in attempting to relay files between the two, in order to attempt test export/import options. They are both very capable programs and though they offer vast options (of which I have scant use), they seem to provide a very capable writing environment. I've been trying out both Storyist and Montage.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |