Jump to content
Storyist Forums

Steve

Root Admin
  • Posts

    3,970
  • Joined

  • Last visited

Posts posted by Steve

  1. Hi TomGom,

    Storyist for Mac can open Scrivener files. Just launch the app, choose File > Open, and select your Scrivener file. Storyist will create a new project, which you can save wherever you want.

    Storyist can save images. It doesn't store pdf or epub, but you can export using these formats from your project.

    If you keep your Storyist files in iCloud, they'll be automatically synced between your devices.

    -Steve

  2. Hi Toni,

    I'm glad you were able to reconstruct the document. If it helps, versions of the document from before your edits should also be available in the version history.

    If you'd like to investigate further, let me know at the support address. It sounds like the issue occurred when you changed the name of the file (or perhaps the name of your iPad?) That's interesting. iCloud used to have version issues related to renaming, but I haven't seen them in a couple of years. I'll try some experiments here on iOS 17.3.

    -Steve

  3. Hi luluaussi,

    Storyist periodically makes automatic backups of your project as you work. To see them:

    1. Return to the Storyist home screen.
    2. Press and hold your project document until the context menu appears.
    3. Choose Versions.

    This will show the version history of the file. Make sure that you're connected to the internet so Storyist can find both the versions on your iPad and those stored in iCloud. You can restore to a previous version from here.

    image.png

    If this doesn't resolve the issue, please send an email to support@storyist.com with the details. It would be helpful to know:

    • What version of iOS you're running.
    • What model iPad you have.
    • How much free space you have on your iPad and in iCloud.

    -Steve

  4. Hi Barynz,

    The file format didn't change between Storyist 3 and Storyist 4, and Storyist 4 can open files from older versions.

    I'm happy to help you troubleshoot. Please send a brief email to support@storyist.com with a little more information on what you're seeing. It would be helpful to know:

    • What versions of macOS and Storyist are you running on the 2009 desktop?
    • What version of Storyist are you running on the 2019 laptop?
    • Did the issue on the laptop occur before you updated to Sonoma? (Sonoma has some bugs, and Storyist 4.3.1 has some workarounds for them.)

    It would also be helpful to know a little more about what looks 'blank'. I'm assuming that you can open the projects and that you can see the files in the project view, but that the text is empty. If that's not the case, let me know what you're seeing. A screenshot would be helpful.

    I can also look up your Storyist 2 license if you purchased it after 2011.

    -Steve

  5. Hi David,

    Are you using the Mac or iOS version?

    If you're on a Mac, the best place to start is the Getting Started guide available from the Welcome window. (Window > Welcome to Storyist). This will introduce you to the concepts and give a playground where you can experiment with the features.

    In general:

    Chapters are denoted by styles with a heading level of 1. Sections are separated by a paragraph containing only the "#" character. The Novel template has a stylesheet with a Chapter Title (heading 1) style and a Section (body text) style.

    The Working with Styles tutorial takes you from a plain text manuscript to a formatted one with chapters and sections, and is a great place to start if you're not using the Novel template.

    If your on iOS, you can access the Getting Started Guide as follows:

    1. Tap the New (+) button on the Storyist Home Screen to bring up the template chooser with the available project template.
    2. If you don't see the Getting Started guide, tap the More (...) button and select "Show Getting Started Guide"
    3. Tap Getting Started to create a project containing the guide. You can use this to experiment with features.

    -Steve

  6. Hi Cristy,

    Is the list of manuscripts that appear when you click Open a list of Storyist (.story) projects? Storyist projects can't contain other projects, but they can contain text imported from many other file formats. If you want to collect drafts from from separate Storyist projects into one big project, try this:

    1. Open a project containing a draft you want to move.
    2. Export the draft as an RTF file.
    3. Open the "big project" and import the RTF file you created in step 2.
    4. Repeat for other drafts as necessary.

    -Steve

  7. Hi Dave,

    Good to hear from you!

    RTF (the original Word file format) is still the best way to get documents to Word. Support for .docx is on the list for a future release, although it's been on the list for a while and there are other higher-priority features above it. I probably won't add .doc or Pages support, since they are undocumented proprietary formats.

    -Steve

  8. Hi Hadas,

    Are you creating a PDF for print? If so, there is a setting to do just that in the book format inspector.

    There is more info in the "Creating a PDF for Print" tutorial.

    If you're exporting a rich text file, you'll need to do this substitution before exporting. Here's how.

    1. Create a copy of your document. (Select the file in the sidebar, right click, and choose Duplicate).
    2. Use search and replace to change "<Paragraph Break>#<Paragraph Break" to "<Paragraph Break>* * *<Paragraph Break">. You can use the Insert Pattern command from the search field pulldown to insert a paragraph break in to the search and replace fields.
    3. Export your document.

    Note that after replacing the section separator, your sections will no longer be marked as distinct. That's why you'll want to do the search and replace on a duplicate of your file.

    -Steve

    Screen Shot 2022-11-04 at 11.22.45 AM.png

    Screen Shot 2022-11-04 at 11.27.14 AM.png

  9. Hi Cristy,

    Thank you for the screenshots. I notice that you have "Correct Spelling Automatically" checked. Is automatic correction what isn't working, or are you not seeing misspelled words underlined correctly?

    It would be helpful to see a sentence or two of what you're seeing in Storyist, and also see that same sentence in Text Edit. Storyist and Text Edit both use the spell checking system in macOS, so you should see the same result in both for the same Spelling menu settings.

    Some things to try:

    1. Temporarily turn off grammar checking. Apple has been experimenting with machine learning on Mac, and the results can sometimes affect spell checking results.
    2. If you've ever installed Grammarly Desktop for Mac, see Uninstalling “Grammarly for Mac” app breaks “Check Spelling While Typing”.

    -Steve

  10. Hi Cristy,

    Make sure "Check Spelling While Typing" is enabled in the Edit > Spelling menu.

    If that's not it, please let me know a little more about your setup. It would be helpful to know:

    • What language is set in the Keyboard > Text pane in your System Preferences. The default is Automatic by Language.
    • What version of MacOS you're running?

    -Steve

     

    Screen Shot 2022-08-09 at 11.43.58 AM.png

    Screen Shot 2022-08-09 at 11.49.19 AM.png

  11. Hi Bob,

    I just switched back to a 12.4 machine, and am also seeing some weirdness. Storyist uses the built-in spell checker in macOS. It's the same one that TextEdit and other apps use. Here's a video from TextEdit.

    I'm going to have to do some research to see what's going on, but unfortunately this is a macOS issue, not a Storyist issue.

    Are you using an M1 Mac or an Intel Mac?

    -Steve

  12. Hi Bob,

    Do you have Spelling > Correct Spelling Automatically enabled in addition to Spelling > Check Spelling While Typing? If you're just looking to have the app add the red underlining to spelling errors, you'll want to turn off Check Spelling While Typing.

    If that's not it, could you post a screenshot of the Keyboard > Text pane in the Preferences window?

    -Steve

  13. Hi Chris,

    The fix for the word count field went out to the beta group on Friday. If you'd like to try it, please send an email to the support address and I'll send you the link.

    The drag & drop issue will take a little longer. In the mean time, you can rearrange the fields as follows:

    1. Remove the field from its current location if necessary by clicking the field label and selecting Remove Field from the menu.
    2. Click the field after which you want to place the new field and select the new field from the Add Field menu.

    -Steve

  14. Hi Chris, 

    Thank you. Let me ask you a few questions:

    1. Are you using the Word Count field? It looks like some changes in Big Sur can cause Storyist to crash when updating the word count. I'll have a fix for that shortly. Send an email to the support address if you'd like to try the beta.
    2. Are you using custom fields? If so, could you let me know the type of field (Text, Character, etc...) you created?
    3. You mentioned that two of the three crashes occurred when rearranging fields. How are you rearranging them?

    -Steve

  15. Hi Chris,

    I'd be happy to look into this for you. Unfortunately, I don't see any crash reports for exporting issues. Crash reports are anonymous. Could I ask you to reproduce the crash and include a reference to this discussion when you submit it? If I can reproduce it here, I'll fix it for you right away.

    Also, could you double-check that you're running Storyist 4.2.5?

    -Steve

  16. Hi Kubrick,

    I'll move it, if that's ok with you. That way, other's might be more likely to see it.

    I assume you're using iOS 15.3 or 15.4 and Storyist for iOS 4.3. If that's not correct, please let me know.

    Do you have a short sample that you could send to support@storyist.com that causes your device(s) to crash? I'm guessing that there is something in the content that causes the crash.

    Also, try turning off Speak Selection in the Settings app. There is an iOS 15 bug that causes apps to run out of memory when you bring up the selection menu on a large file.

    -Steve

     

  17. Hi Cargil,

    I've spent some time investigating this. Technically, it is possible. Unlike Gammarly, ProWritingAid provides an API for developers to use to integrate the text checking service with their app. There are some challenges, though.

    ProWritingAid charges for each call to their API, so it's not something Storyist could offer for free. There would need to be a reasonable monthly subscription fee for the feature. Alternately, Storyist could let you sign into your ProWritingAid account with your personal subscription (that you pay for separately), which would allow you to use it from your browser too. Unfortunately, the ProWritingAid API doesn't currently support such logins, so this approach would require changes from them.

    Also, in the past, Apple has rejected apps that don't use their in-app payment system (this approach would not), which would mean Storyist for iOS and Storyist for macOS purchased through the Mac App Store might not get this feature.

    As you've probably noticed, the spell checking on macOS has gotten worse over the last couple of OS releases, so this is something I'm actively looking at. Unfortunately, I don't have a timeline yet.

    -Steve

×
×
  • Create New...