Jump to content
Storyist Forums


  • Content Count

  • Joined

  • Last visited

Everything posted by marguerite

  1. 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
  2. You're most welcome. If you run into difficulties, just post--or send an e-mail to support at storyist dot com. The developer is usually very responsive. Best, Marguerite
  3. 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
  4. 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
  5. 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
  6. I checked, and I see only an overall word count. In the Mac version, the word count changes when you select text, so you can easily get a word count for one section or a chapter. But when I selected text in the iOS version to check, the word count remained the same. I don't use the iOS version much, though, so there may be another method that I don't know about. Best, Marguerite
  7. See my response in the other thread. Was it the iPad version you were using, then?
  8. Hi, Cargil, That was probably the Word grammar checker, since its and it's are both correct spellings, depending on the context. Which version of Storyist are you running? Since I'm working with beta versions, I'm not always sure which feature is in which release version (and I don't use grammar checkers, as my grammar is better than Word's). But if there is a fix, the version number is the place to start. Best, Marguerite
  9. I don't use index cards much, but do you know you can set the colors of the cards in Storyist and track them that way? You can move the cards around on the corkboard as needed or use the colors as a visual identifier. See the attached screen shot. In the left window, the colors separate the months, so all of September is pink, etc. In the right window, the colors identify the POV character (orange=narrator, blue=hero, purple=heroine, yellow=main subplot character who is also the heroine of three other books in the series). Sorry for the slow reply. I thought someone else would answer, because most people use the index cards far more than I do. Best, Marguerite
  10. It is a text file. The confusion is that the red-tipped ones are also text files, but they originated in the Notebook (in an earlier version of Storyist), so they behave differently. When Steve set up Storyist to import Scrivener files directly, he replicated the different structure of Scrivener files by using those former notes to represent the individual scrivenings. And that's pretty much the limits of my technical expertise. I've been using Storyist since 2007, so I have always set up my novels as in the second screenshot above. And because I'm writing a series with overlapping characters and settings, many of my files have been rolled over and repurposed since version 1. The only thing I use the red-tipped files for are my blog posts, where it's useful to have each one treated as a separate piece. As a result, I can't help much more than I have already, beyond that basic explanation. As far as Storyist is concerned, red-tipped text files are separate, and text files with an icon that looks like two pages with writing on them are single manuscripts, no matter how large. Best, Marguerite
  11. Is this your manuscript that is breaking into sections? If you see something on the side of the screen that looks like this: then each of the red-tipped notes is a single file, and exports as such. If you see something like this: then you have a single integrated manuscript that should export as one file. If you imported the file from Scrivener, it takes the first form automatically, because that's what Scrivener's sections are (separate files). If you create a new file via New > Project, and pick, say, the Novel template, you should get the integrated file shown second. If you've done one and worked on it and want the other, though, I think that can be laborious to do. Steve may have a better solution. If, instead, you're referring to each character or setting saving as a separate RTF or RTFD file, that's deliberate. You can merge the files on export by choosing File > Export, selecting Outline next to Export and RTF as the format, and clicking on the files you want to merge. But you won't get everything, just the summaries. Hope that helps, Marguerite
  12. You're welcome! Sorry it didn't solve the problem, but I did remember after posting that I had encountered such behavior occasionally in Storyist under Mavericks (I upgraded directly from Mavericks to High Sierra). Something would cause a crash, and Storyist might report itself as shutting down unexpectedly two or three times in a row, even when I was quitting normally. So it may have nothing to do with the new OS. Best, M
  13. This may be out of left field, because I haven't had this particular problem with Storyist and High Sierra, but I have run into problems with InDesign CS6 and the latest version of iTunes (12.7?) running on High Sierra, including exactly the behavior you describe. I don't even need to be playing music for ID to slow to a crawl and crash on exit; if iTunes is running, that's enough. It happened once before with iTunes and Microsoft Office, otherwise I'd never even have thought of the possibility. Best, Marguerite
  14. Hi, Wankled, and welcome to the forums, Storyist doesn't have an exact equivalent of Scrivenings mode, because a native Storyist manuscript is a single file, like a Word document. If you are importing files from Scrivener, you won't see that, because Storyist imports each Scrivener segment as its own text file (a solution is to merge files in Scrivener before importing). You can split the screen and view files side by side, including in different modes (as text and index cards or text and images, etc.), but you can't select a group of text files and temporarily merge them on screen as in Scrivenings mode. You need to keep the Project View open and go quickly down it with the cursor to pop each file onto the screen one at a time. Best, Marguerite
  15. Hi, Dan, You can't change the section break character and still keep the section functionality, because the # is how Storyist defines a new section. You can, however, change the section break character before printing or sharing with friends. Just duplicate the file (because you're about to wipe out all the sections), then in the duplicated file choose Edit > Find, click on the box next to Replace, then enter # in the Find bar and whatever character you want in the Replace bar. Choose Replace All and you're done. Best, Marguerite
  16. Hi, Jewell0607, and welcome to the forums! Default Style is Storyist's backup way of not upsetting the formatting on imported text (at least, that's my experience of it—I'm a user, not a support person). So if you copy and paste from Word or even from one part of Storyist to another, say the Notebook to your manuscript or vice versa, it tends to acquire the label of Default Style. I'm not sure why you're seeing the Default Style formatting change, but the easiest way to get around it is to avoid using Default Style in the first place. The solution is to set up the Section Text, Section Separator, Chapter Title, and other styles in the manuscript to have the fonts and attributes you want, then apply those to your text. You can do the same thing in notes with Body Text, etc., but the changes are unique to each note. Those styles will not change once you set them. At least they should not. You may want to try it out on a few paragraphs first to be sure. If they do, then you have a different problem, one that, most likely, only the developer can solve. In that case, your best bet is to send a message to support at storyist dot com. While actively working on a manuscript, I also keep a second manuscript in the same project called "Saved Scenes" or some such thing. If I want to get a scene out of the manuscript but am not sure whether I can do something with it later, I copy that section and save it as a section in Saved Scenes. Then I can restore it if need be. Another option is to Save a Version and add a comment so you know which version has the scene. Either of those methods will avoid having the text revert to Default Style. Hope that helps, Marguerite
  17. Well, there are a couple of misunderstandings here. First, although the files people read on Kindles are AZW, a variant of MOBI, authors can upload ePub files to Kindle Direct Publishing, which will convert the ePub files to Kindle format. Second, although the Kindle is the bestselling e-reader (I think) and Amazon controls much of the e-book market, other popular devices like iPads or iPhones running iBooks or Sony/nook/Kobo e-readers do require the ePub format. Third, Storyist lets you export files in both ePub and MOBI formats, to give you the broadest reach. If you read only on Kindle, you would want to export your e-books as MOBI. But I read mostly on iBooks, so I export them as ePub for my own use and as MOBI for Kindle users. I also use Calibre to convert the Kindle books I purchase to ePub, if they aren't protected, because I prefer having all my books in one program as much as possible. Hope that helps clarify the situation. Welcome to the forums! Marguerite
  18. Depends how comfortable you are digging into the program. Steve posted instructions here: http://storyist.invisionzone.com/index.php/topic/2311-editing-character-sheets/?hl=%2Bcharacter+%2Bsheets I assume they still work with version 3. Best, Marguerite
  19. One note from someone who uses both Storyist and Scrivener on Mac (I prefer Storyist, but my work projects have many, many footnotes) and has tried to exchange files with writer friends who use Scrivener for Windows. The two versions of Scrivener are not compatible: that is, Scrivener for Mac can't open Scrivener for Windows files and vice versa. So Storyist is actually a better option for working with Scrivener for Windows files on the Mac than Scrivener itself is. Weird, I know, but that's been my experience. Best, Marguerite
  20. Yes, it can, so long as the version you have is compatible with the OS on your new Macbook (Storyist 2 is not compatible with El Capitan, e.g.). Download the latest version from http://storyist.com/downloads/ and install it. If you go to Library > Application Support > Storyist (the Library is hidden by default, but go to your home folder, choose Go to Folder from the Go menu in the Finder, and type ~/Library in the box that appears, and it should show up), see if there's a file called .storyist3license (or storyist2license, depending which version you have). If there is, that's your license code. I think you can just drag it onto the application icon to register it. If not, or if you encounter any other problem, send an e-mail to support at storyist dot com, and Steve will send you your code. Best, Marguerite
  21. If it's helpful, Ginger, there are 12 points to a pica and 6 picas to an inch: so 1 in = 72 points. The system allows for very precise measurements during typesetting, so folks like me use picas and points by preference. Looks like Steve's on the technical issues, as usual! Best, M P.S. These posts are making me glad I didn't upgrade to Sierra, which seems to have a number of problematic behaviors.
  22. Hi, Circidon: Welcome to the forums, and congratulations on getting so far with your novel! To answer your questions: 1. Since we can assume your beta readers will not have Storyist themselves, the easiest options are to export to either e-book formats (Kindle, ePub) or to RTF. Storyist does both of these things well. Which you choose would depend on what you want back and which stage of the process you're in. E-books are good for final reading, assuming the beta readers have the right devices, and readers can make notes while reading, although they will have to construct separate files in a word-processing program to send to you. RTF files can be read directly into any version of MIcrosoft Office, Open Office, Pages, or even TextEdit (but be aware that Pages and TextEdit keep your formatting but trash your RTF styles, which creates problems if you try to read the files back into Storyist). The readers can then enter comments directly into the documents for you. Google Docs operates similarly, although personally I don't like how Google Docs handles formatting. 2. When you say "export a Storyist document to a publisher," do you mean an editor at a traditional publishing house? In that case, it's easy: you export the file to RTF, load it into a word processor and resave as .doc or .docx, and send it out. If you mean to a printer like CreateSpace, you have to set up the formatting and the page size in Storyist, then print the file to PDF. It's not difficult, but it assumes you have a basic grasp of styles and how to work with them. Hope that helps, Marguerite
  23. This has come up before. Often the culprit is frequent saving of the file, which forces Storyist to create a new version every time. I don't have El Capitan, so there could be something else going on. But I do date from the generation burned by Word's tendency to crash and kill an hour's work, so I hit Command-S every few minutes without even thinking about it. I've had to retrain myself for Storyist. (Alas, Word remains as cranky as ever.) Might be worth a try. And welcome to the forums! Marguerite
  24. If it's a single page or a couple of pages, as is typical with a web page, then open the PDF in Preview and export the pages one at a time to PNG or JPG. You can then drag those onto a Storyist note as if it were any other graphic. Note that doing so may dramatically increase the size of your file if you have hundreds of articles, but so would dragging in PDFs. With text-heavy pages, I just copy the text and paste that into a Storyist note, then add the link for the page. You can go through the text once in Storyist to eliminate callouts for pictures, etc., if needed, but it doesn't capture every darned thing as the PDF does. If you're worried that the page may disappear, you can save the PDF as backup, but you'll still have most of the information in Storyist with minimal effort. People have asked for the feature before. It would be useful, but only Steve knows where or if it is on the schedule for implementation. There may be technical issues to solve—or just not enough interest compared to other requested features. Best, M
  25. Hi, Lawrence, I have seen pagination change from the Mac to the iOS versions, but I use the iOS app only for correcting text after I've shut down my computer, so I can't help. For me it's not a problem because it goes back when I reopen the file on the Mac. Have you tried adjusting margins? Or checking to see if Widow/Orphan protection is included in the latest iOS version? I think those are the most likely culprits for what's causing the discrepancy. Steve will probably be around soon to respond. Best, Marguerite
  • Create New...