MarsEdit 3.6.3 is available now from the MarsEdit home page, and has been submitted to the Mac App Store for review by Apple.

This release addresses a few stability issues and some subtle usability problems related to image workflow and full-screen integration on Mavericks. It also fixes a nagging issue for Tumblr users who preferred to have images remain in the same format as they provided. Previously the images were unilaterally converted to PNG format.

Here is the complete list of changes for this release:

• Fix to Tumblr image uploads to preserve original image filetype (e.g. JPEG)
• Fix a bug where image sizing constraints were enabled even when full-size option selected
• Fix a bug that prevented reliable searching/replacing of multiple spaces in Rich Text mode
• Fix a crash that would occur if the “Send to Blog” button was clicked twice instead of once
• Fix an issue with OS X Mavericks where window positions changed when switching from a full screen app to MarsEdit

Please let me know if you run into any issues with the update!

The folks at WordPress.com have great news for fans of Markdown. It’s now built-in by default to every WordPress.com blog, and it’s super-easy to enable:

To start using Markdown, go to Settings → Writing in your blog dashboard, check the box next to Use Markdown for posts and pages, and save.

I just enabled it for one of my test blogs and am happy to report that MarsEdit works perfectly for publishing with Markdown to WordPress.com. They mention that it’s best to stick to the “plain text” editor on WordPress.com, and the same is true for MarsEdit. You’ll want to stick with editing in “HTML Text” mode so the plain Markdown text can get to your blog without being wrapped in HTML generated by MarsEdit’s rich editor.

I wrote recently about MarsEdit’s ability to automatically convert Markdown to HTML before publishing a post. It’s worth noting that if you use the new Markdown functionality on WordPress, you probably want to avoid MarsEdit converting to HTML. This is because WordPress’s implementation of the Markdown feature does things “the right way” in my opinion, storing the original Markdown as the text of the post, so you can make further edits to the post by editing the original Markdown and not the converted HTML.

The only downside I’ve noticed so far is that when you download a post through the API from MarsEdit or from the official WordPress apps, the content is converted to HTML even though it shouldn’t be. The original Markdown does show up in the web-based WordPress admin panel. I’m going to report this as a bug and hopefully they will agree that it should be fixed.

All Red Sweater apps are compatible with OS X Mavericks.

Over the past-several months we have tested all our apps against pre-release versions of OS X Mavericks. Minor bug-fixes were required here and there but have been actively deployed in the released versions of apps for several months.

Should you run into any issues at all with OS X Mavericks, please get in touch and we will make it a priority to address any outstanding compatibility issues as soon as possible.

For years, MarsEdit has supported Markdown in a manner that makes it easy to write, preview, and publish to a blog without ever dealing in HTML or Rich Text.

However, for years it has also been confusing how exactly one goes about using Markdown with MarsEdit. Because there is no explicit “Markdown mode,” many people assume there is no support for Markdown. I agree that Markdown should be more explicitly supported, but the extent of Markdown support in MarsEdit may surprise you.

To assist customers who wish to write in Markdown when publishing to their blogs, I present these guidelines for making the most of MarsEdit. Note that if you happen to want to use another markup script such as Textile or MultiMarkdown, these guidelines also apply.

Guideline 1: Edit In “HTML Text” Mode

MarsEdit supports two modes of editing: “HTML Text” and “Rich Text.” It’s important to appreciate that in Rich Text mode, everything is converted to pure HTML before publishing to your blog. There is no room within “pure HTML” for Markdown to exist. Any Markdown content will be wrapped up in pure HTML tags, which prevents the Markdown from being rendered either by MarsEdit’s preview window or on your blog.

In MarsEdit, “HTML Text” is a synonym for “unadulterated markup.” It’s called HTML Text because that’s what the majority of users understand it to be useful for. In fact, you can type arbitrary text content in “HTML Text” mode and MarsEdit will not alter it, with one exception that I’ll get to later.

In MarsEdit’s preferences, you can opt to have posts open in “HTML Text” mode by default. Alternatively, you can switch to HTML Text mode at any time by selecting Post -> Edit HTML Text.

Guideline 2: Set The Preview Filter To “Markdown”

MarsEdit supports a flexible preview system designed to simulate how your blog content will look after it is published to the site. The two main components of this system are the preview template, which consists of arbitrary HTML with placeholders for your blog entry contents, and the preview filter, which transforms the content of your post to simulate server-side transformations.

By default, MarsEdit uses a preview filter called “Convert Line Breaks,” which simulates the common behavior across many blog systems of converting blocks of text separated by two newlines into “paragraphs.” This is what enabled you to write in “HTML Text” mode with paragraph clumps, and have it appear in the preview window as paragraphs, even though strict HTML would treat those clumps as a contiguous block of text.

Markdown is also included as a built-in preview filter, so you can write your “HTML Text” using Markdown syntax, and see how it will look after your blog processes it.

This assumes your blog knows how to process Markdown. Some blog systems include Markdown support by default, but many do not. If your blog system doesn’t understand Markdown by default, pay close attention to the next and final guideline.

Guideline 3: Convert Markdown To HTML If Needed

Generally speaking I encourage Markdown fans to keep their content in Markdown format when possible. For example if you publish a long post and want to go back to make substantial edits later, it will always be preferable to have the original in Markdown format.

Unfortunately preserving content in Markdown format is not feasible for all blogs. If you are publishing to a blog system that does not recognize Markdown, and you can’t for example install a custom WordPress plugin to facilitate such recognition, you will need to see that your Markdown content is converted to HTML before publishing.

Starting in MarsEdit 3.6, a new per-blog option makes it easy to automatically convert Markdown content to HTML when you publish to a blog.

Simply check the “Apply preview filter to content” box in the blog settings for your blog, and whatever preview filter is configured for your preview window will also be applied to the content before submitting it to your blog. This is the great exception to my previous promise that MarsEdit will not alter your content in “HTML Text” mode. If you check this box, your content may be dramatically altered, but hopefully to your great delight.

Guideline 4: Have Fun

Experiment with MarsEdit’s versatile previewing system, and let me know how the Markdown support is working for you. I have ideas for improving it even further, but your feedback will help to clarify those ideas as I move forward.