We've begun .fountain support but it isn't fully baked yet, so we're aware of some bugs, particularly with import. Please go ahead and report anything you do come across, though, so we can be sure it's on the list. Regarding the formatting, it would be helpful if you could also include the ruler in screenshots and let us know if you're using the Fixed Width editor (set in Options > Appearance > Main Editor). I'd avoid using Page View at the moment, but once that has had some bugs worked out it would be great to get feedback on working with it and script mode.

MimeticMouton wrote:We're talking about the buggy way the text is wrapping on the right edge, yes?

I was actually also talking Indent, Line length and Spacing, but I've been playing in the settings and I think I can change that. I assume the stable version will come with the standard screenplay measures as default, right?

If you don't mind me showing you a screenshot from another program to better explain what I mean.

MimeticMouton wrote:Are you getting that in a fresh blank project, switching into script mode (screenplay) and typing?

Ok, so I did some testing and the wrapping of the text only appears on the imported Fountain files. The blank project just has the wrong indenting, etc..

I think part of the issue here is the difference in the way the indents work. Scrivener's editor, in this wrap to editor mode, is measuring out from the inside of the left margin, so where it's showing 1.5" on the ruler, when you compile using a 1" margin, that's the same as 2.5" in the other view that's starting with 0 as the left edge of the page. This comes from Scrivener's methodology of separating the drafting from the formatting and layout; since the compiled product may be formatted differently from how you work in the editor, the editor doesn't represent a physical page.

Understandably, the formatting in scriptwriting vs. a novel or such is much more structured and how it fits on the page is important for time estimates, so this is the main purpose of the Page View feature we're in the process of implementing. While Page View won't necessarily mimic the final compiled output, for something like scriptwriting, where the formatting used in the editor is typically exactly what you want to output (without changing font face or size or such), when you set up Page View with your paper size and margins, it will give you a closer visualization of what your end product will look like. That will then more match what you're showing in the second screenshot.

The script settings are all customisable, but the intent is to supply some useful defaults, such as standard screenplay formatting. If the spacing or such is not matching what you expect, could you provide a specific example and reproduction steps, and a link to the formatting specs you're referencing? Whether it's a bug with how text is displaying in the editor or an incorrect setting in the script format, we'll want to check it out. I do know that some of the script formats need to be reset, so I'll add any notes you have. Thanks!

First off, every time I try to change the Script Settings, Scrivener crashes so it's been a bit hard to test.

I think the extra "margin" you mentioned doesn't factor into this since it's not a compiling / printing problem but a view problem in the editor.

I tried to change the Script Settings to comply with the standard but even though the metrics are the same, it doesn't look anything like the standard format. Compare the screenshot below with the one I took earlier from Fade In.

Even though the action lines start from about 1.5 inches to 7.5 inches, in Fade In the text "We’re underwater, watching a fat catfish swim along" fits in the line (like the PDF of the script using the standard formatting), while Scrivener cuts the line off at "fat". The width is not the same. I don't really understand why. The font size is the same. 6 inches should be 6 inches everywhere.

I think the ideal screenwriting environment on a program like Scrivener doesn't necessarily include "Page View" (though that's a really nice tool too). There are things you don't need when writing a screenplay: scene numbers, page numbers and page breaks. Some will disagree about the last one - the ideal writing environment is obviously not the same for everyone. I prefer to break my screenplay in sequences and only worry about page breaks after finishing a draft.

The current metrics don't work because it's hard to write with such narrow width. A larger width would attenuate that problem but the standard format would be best because you need to get a sense of how words fit on a page for a variety of reasons.

There are things you don't need when writing a screenplay: scene numbers, page numbers and page breaks. Some will disagree about the last one - the ideal writing environment is obviously not the same for everyone.

I disagree. For me (and I think the majority of working screenwriters), page breaks and accurate page counts are absolutely necessary.

FWIW, Final Draft took over the market back in the day because it was the first app to provide WYSIWYG screenplay formatting, including page breaks and page numbers. Prior to that, people wrote in a continuous scroll in a word processor, and then fed the file to a screenplay formatter to see their page breaks and counts.

Also, you don't need scene numbers until there's a UPM breaking down your script. Your draft should be migrated to Final Draft, FadeIn or some other production-ready app for that.

Yeah, but L&L has such a small sample size for screenwriters, I don't want them getting the idea that your preferences represent the market at large. Page breaks and page count are features that the majority of screenwriters want and need.

Sorry for the delayed reply here! RLeal, thanks for the follow up with the screenshots and further explanation--I see what you're talking about now, and yes, actually, this is a general character-per-inch display scaling issue that we're working on resolving. You'll find unfortunately that how it wraps appears differently depending how the editor is zoomed or how the Windows display scaling is set, and of course this is most noticeable in script formatting. Thank you also for the additional formatting links.

The hang occurring when converting script elements (occurring when script text already exists in the project) is also filed.