Save
Saving
• mz2

The free application allows you to write up to three documents that reach a word count of 1,500 words, after which you are prompted to purchase a "Manuscripts Unlimited" license code that removes document count and length limitations.

• The license code allows activating the application on up to three computers.
• The license code does not expire (the activation state of the application version you've downloaded will persist).
• If you are a student, a 50% student discount applies when purchasing the unlimited license code.

## Installing and Running Manuscripts

2. Open Finder and drag the un-archived Manuscripts.app bundle to /Applications or ~/Applications.
• NOTE! It is important to drag the app either into /Applications** or to ~/Application (Applications folder under your home directory) rather than using it from e.g. ~/Downloads, because macOS is guaranteed to register its Spotlight and QuickLook support only once this has been done).
3. Launch the app you placed in the Applications folder (double-click in Finder, or click it in the Dock).

posted in Knowledge Base read more
• mz2

@Timothy-Morgan could you send us the document via support@manuscriptsapp.com, please? Does copying and pasting to Word give a workable workaround until we resolve this document specific issue? I'm very sorry for the trouble!

posted in General Discussion read more
• mz2

@Charlie as noted on Twitter earlier, we don't do this automatically because it's not behaviour that most authors would expect to happen automatically. That is, I'm assuming here that Markdown support overall is a power user feature, whereas majority are using Manuscripts simply as a capable rich text editor. I think this feature makes a lot of sense though – it would make sense for us to add it in the Edit > Resolve menu where we already offer resolving Markdown syntax (which  arguably is or is not, so makes sense perhaps to add it as a separate item).

• mz2

@ringlery, @schury I recognise this is definitely one of those features that makes all the difference for specific authors (based on the journals you need to target), and makes the difference between being able to directly use the DOCX file exported from Manuscripts, or having to tweak it with MS Word or similar tool after.

As an aside, we indeed have not completed all feature requests in a bit less than 2yr

posted in General Discussion read more
• mz2

@ming thanks for reporting this – the Bookends library import function and this "Bookends Bibliography Search" both check for the existence of the app in order to enable or disable themselves, and the Bookends Bibliography Search check was not taking into account the Mac App Store distribution of Bookends. The fix I've made for this will be included in the next (free) update to Manuscripts. Thanks!

• mz2

@OlgaM, @clarkn, @vandersonpc , @sean.h, @AdamCatalyst , @mke I believe we've addressed the primary sources of instability for the next free update. Sorry for the delay with this update, but it should greatly improve the stability as there appears to have been a primary (pretty document specific) remaining crasher still out there (we measure the crash rate and have continued to see an overall improvement but specifically spiking repeated crashes with some users). The crasher has to do with some of the background processing the app does with the documents it keeps computing word counts, and tries to do so only when the rest of the system is idle, but that logic has now been improved.

posted in General Discussion read more
• mz2

@Charlie looks like it's time for us to communicate clearer our support procedure: there is 1:1 support available via support@manuscriptsapp.com, available also directly from the app. As I've noted time and again on this forum, this is a forum where I (the primary author of the app) pop in every now and then, but this forum we provide is really a community maintained resource. I'll do my best to make this clearer still on the website and on the forum itself. Reason we've kept things in this way is because the prompts in the app itself for reaching for 1:1 support are the most visible support mechanism, but given this is recurrent confusion now, we'll do our best to improve on it.

• mz2

@OlgaM noted – we need to provide more text formatting for captions. Font size and weight / italic are on our todo.

posted in General Discussion read more
• mz2

@rosslyn the challenge with meeting this feature request is that there is no standard to how citation tokens are marked up in Word documents – Papers, Mendeley, Zotero, F1000, EndNote (indeed different versions of EndNote) all expect different conventions, and no-one documents their conventions (Zotero we can work out most straightforwardly because it's open source).

@hubob is right though in that we hope to tackle this by promoting a collaboration mode where you don't need to export Word documents but can annotate documents collaboratively. We're basically ready for beta with it, have continued to polish it whilst we work on an unrelated issue that has prevented us from releasing this feature yet.

• mz2

@jonasludvigsson OSX 10.11 is the oldest version of macOS supported for Manuscripts and there never was a version that supported an older OS. This is for multiple reasons, chief one being that as things stand on Apple platforms, Apple makes it very difficult to both move forward and support new OS features, and to be backwards compatible with older OS versions – development tools targeting the currently newest macOS in a form that allows taking use of the new features (and in a lot of cases platform bug fixes) only work on the new OS, and these tools themselves don't even anymore include everything needed to test and run things targeting older OS versions. Things are moving especially fast into this direction with the new programming language they've announced even (we are using Swift 3 indeed inside Manuscripts). I'm personally not a big fan of very limited backwards compatibility but as an indie product team we are kind of limited by the realities

• mz2

@Elio you can simply simply copy and paste a picture in place when you have a location selected in the editor where you'd like to place the figure in. The one caveat I am aware of is that you cannot currently use copy & paste to replace an existing image, for that you need to click on the image and drag the picture in, or choose it from the File dialog.

If this is not working for you, could you tell us which application you are pasting from and what format the image is?

• mz2

@ehurtado thanks for the kind words! This is definitely heard loud and clear and we look for ways to improve on this, and I believe we have a pretty good solution in mind that hopefully improves our responsiveness. The basic limitation at the moment is that we are a tiny team and at times it tends to be more effective for us to work on an update and then respond in batch on those items we've taken up and addressed in the update. This leaves much to be hoped for in terms of the "median responsiveness" we achieve, even though I've been super happy to see that some community has indeed formed and people are posting helpful messages here on the forum (kind of why I stopped responding publicly here a while ago and focused on the 1:1 support time, in the hope that this would indeed happen).

• mz2

@bbud02 this is a bit more fiddly than it should be and we should probably add a context menu item for "Add a Citation" to make this easier, but placing the caret literally right next to the existing citation should do it. To rule out document (citation style) specific issues with this working (it's remotely possible because the application has to "search for" a nearby citation), would you mind sending us the document referring to this discussion where this is failing, please?

posted in Knowledge Base read more
• mz2

@tomkaier this looks to be due to a missing script that Manuscripts places in ~/Application Scripts/com.manuscripts.Manuscripts/execute-pdflatex.sh in order to complete the PDF export (we need to place this script in that location because the security sandbox that Manuscripts executes in otherwise doesn't ).

This would happen if you try exporting to PDF without having allowed Manuscripts access to ~/Application Scripts/com.manuscripts.Manuscripts. Did you perhaps dismiss the dialog asking for access to this location, or point the application at another location? That we show such a dialog in the first place is really forced on us because of the security restrictions on macOS – a file open dialog is the only facility provided by Apple for us to request for access to the location.

Would you mind also sending us the document via support@manuscriptsapp.com, please? I'd like to look into the issue with figures and ToC in the Word export case, as neither is as designed of course. The former I believe is resolved in the version pending release, but the latter doesn't sound as expected. I'm wondering if there's something in the section headings that is leading to trouble at the ToC generation stage.

posted in General Discussion read more
• mz2

@OlgaM there's actually a really nice 3rd party app that presents such a cheatsheet for any Mac application: https://www.mediaatelier.com/CheatSheet/ . At this stage I'm hesitant to document listing keyboard shortcuts beyond how they are listed in the application menus because it's precisely the sort of documentation that can very easily go out of date (we very regularly add features with keyboard shortcuts, indeed more often there is a shortcut rather than not), and the menu system on macOS nicely enough always shows the shortcuts, so the value we can provide on top of that is pretty limited, short of going the extra mile like the CheatSheet application does.

posted in General Discussion read more
• mz2

@jonasludvigsson we don't at the moment list them exhaustively indeed beyond the view in the "New Manuscript with Template" dialog – the search field is your best bet for now. We do have noted on our TODO to expose this list also in a searchable form on our website, and overall to allow templates to be crowdsourced from user contributions.

• mz2

@Lawrence-Evalyn you can choose the citation style in Manuscripts itself using the style palette. You can also create footnotes or endnotes directly from the Insert menu. The correct citation style + using a footnote or endnote is what should produce the wanted effect.

• mz2

@bbud02 to merge, the caret needs to be placed right before / after the existing citation.

posted in Knowledge Base read more
• mz2

@Olga-Mielczarek we offer indeed our own mathematical symbol popover that covers lots of characters the standard macOS symbol picker (which we have not suppressed because it can be helpful for other cases) does not contain. The Insert > Symbol sort of symbol insertion tool is actually a special case of the inline equation insertion (which allows using practically any LaTeX math environment character inside the document)… however, I totally agree with you, that we call it "Symbol" is inviting some confusion. I've made a note!

posted in General Discussion read more
• mz2

@cajund there is fortunately a simple workaround to this problem: you can use Manuscripts with Papers directly using the Magic Citations citation tool supplied with Manuscripts.

This issue is most likely caused by there being some unexpected characters encountered when attempting to import the library (Papers itself does some limited form of validation when importing reference data and it can end up exporting data that doesn't go through cleanly in the format that it is exchanged with Manuscripts in). We are working constantly to improve the bibliography import features though (adding workarounds to reference manager specific issues for example) and sending us an EndNote XML (that is the format used when importing the Papers library) export of your library via support@manuscriptsapp.com helps us ensure we've tested the feature with your library before we post the next update. Thanks for your patience!