Recent Profile Visitors

Hi, wappinghigh, and welcome to the forums.
The first thing would be to check, if you are submitting to a literary agent, what that agent's submissions requirements are. Some insist on Times New Roman 12 point; others accept the basic Courier (which is used for the template because it was long a standard); still others don't care about the font, so long as it's not Comic Sans or something similar but have specific requirements for margins. You can change any of the formatting through the Inspector by selecting a paragraph that does not have italics or bold, changing the formatting to what you want, then choosing Format > Style > Redefine Current Style in the menus. You can also click in a paragraph that contains only plain text and choose Format > Style > Edit Current Style and make the changes in the box that appears. Click OK and the changes will be applied throughout the document, with the italics and bold text preserved.
In this case, you probably need to adjust the margins to 1" all around and make sure that the format is double-spaced rather than a set distance. But no one I ever contacted counted lines per page. So in that sense you are fine with the standard setup.
Best, Marguerite

I haven't encountered this behavior. The developer always wants to hear about crashes. Did you report it to the Support address (bugs at storyist dot com)?
He'll also need to know which version of the Mac OS you're running.

So the issue is that when you add a scene in the Screenplay template under Mojave, you get both a new scene and a scene called #?
What happens if you click on the # in the manuscript? Does it have the Section Separator style applied? Does the blank line have the Section Separator style, or is it Scene Heading (Section Text in the Novel template)? If you change the blank line to Scene Heading/Section Text and the # to Section Separator, does that fix things?
Best, Marguerite

Sorry, Outflare, I missed this one the first time. Click on the Inspector icon at top right to open the Inspector. Click on Chapter 1 in the Project View. Click on the paragraph mark in the Inspector and scroll down until you see Page Numbers. Click on Page Numbers to expand it, and you should see two choices: Use default value (selected by default) and Start at. Click in the button next to Start at and you should be able to set the value back to 1.
I checked this in the release version to be sure I wasn't giving you false information based on the beta I'm currently using.
Best, Marguerite

Hi, Robin,
If you go up to the message where Callista originally posted the icon, then Control-click (right-click) on the image itself, the forums will give you the option to download it (assuming you're on a Mac—not sure if the same process works on an iPad or phone).
Welcome to the forums!
Marguerite

No, Storyist is not abandonware. It's still in active development. Where did that come from?
And I expect it works fine with Mojave, as the developer is usually quick to test these things. But I think my Mac's too old to run Mojave, so I can't confirm.

Hi, patamystic, and welcome to the forums!
I don't publish through Blurb, so I may not be completely accurate about this, but I think the Blurb templates are available via the File menu after you create the new project.
So you would choose File > New > Project and define the type of project (novel, screenplay, etc.), by picking the appropriate template. Then you write your book. When you get ready to format the finished file for Blurb as a PDF, you choose File > New > Book with your book project open and access the Blurb templates from there.
Best,
Marguerite

It sounds like a bug. The best thing is to report it, just as you do here, by sending a message to bugs at storyist dot com.
That will generate an issue tracker and send a message to the developer. He's usually very responsive.
Marguerite

Speaking of which, the Mac shortcut is great, but when used by accident, there's no easy way to go back to where you were before (or is there)?
Answer: click the back (left-pointing) arrow in the blue status bar. If it takes you to one stop before, click the forward (right-pointing) arrow. That should get you where you want to go.
On the iPad, I don't know of a keyboard shortcut, but you can tap the three lines at top left, then the circled i next to the name of your manuscript. That gives you access to the entire structure of the MS, and you can scroll down and tap wherever you want to end up.
Best, Marguerite

Hi, WMH99338,
Welcome to the forums! One thing to note right away is that each little piece of a Scrivener document is a separate file, so although Storyist can open the file directly, you may prefer to process it a bit in Scrivener first. I just went through this yesterday with a novel that I plan to revise.
The most efficient way, I concluded, to blend the separate scrivenings into one manuscript is to compile the file to RTF. You want Scrivener to use # as the separator between text files, to leave off any automatic numbering, and ideally to start each chapter with the word "Chapter"--as in Chapter 1, Chapter 2, etc. If you do that, you can import the RTF into Storyist rather than the whole .scriv file. (Or, if you have many notes, you can open the Scrivener file first, save it as a Storyist file, then replace the actual MS with the imported RTF file.)
Storyist will recognize the # as indicating a new section. From there you can use the Apply Styles by Matching Text option from the Format > Style menu and correct any formatting, ensuring that you change fonts in a paragraph that has no italics, etc., before choosing Format > Style > Redefine Style from Selection. If necessary, use the "Choose Stylesheet" option, also under Format > Style, and select the Novel Stylesheet before applying styles.
I actually managed to mess up both the Chapter and the # on the compile, but I've worked with Storyist for (gulp) 11 years now, so I fixed the issues with minimal problems. And the reason I was doing this is because although I appreciate the ease of setting certain compile preferences for e-books in Scrivener, I much prefer Storyist for day-to-day work. Like you, I just find it more intuitive. And I haven't even tackled Scrivener 3, which appears to have an even higher learning curve than its predecessor.
Wishing you luck with the transfer!
Marguerite

I don't know how to fix it, no, but have you tried e-mailing support? In this case, I would write to bugs at storyist dot com (since this obviously isn't intended behavior) with details of what version of the operating system you're running, the model of Mac or iPad you have, and, if you know how to retrieve it, the crash log.
Best,
Marguerite

This is really a Scrivener problem, rather than a Storyist problem. I have a vague sense that there is checkbox in the Compile panel that says something like "Convert footnotes to endnotes on export." In that case, you can try unchecking the box and see what happens. But as far as I know Scrivener always converts footnotes to endnotes.
On the spacing problem, you'd really need to ask someone on the Literature and Latte boards. My guess is that there is spacing in the file that gets converted to spaces in the PDF, since that's what PDFs do: create a stable version showing what will print.
In my experience, the results of Scrivener export are somewhat flawed, other than for creating e-books. But in any case, the main interaction between Storyist and Scrivener is that Storyist can import Scrivener files directly so that you can work on them in Storyist.
Note that Storyist does not have a simple way to handle footnotes or endnotes. It is primarily aimed at writers of novels, screenplays, blogs, etc.—that is, genres that typically do not include annotation.
Best, and welcome to the forums,
Marguerite