Save
Saving
• 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