Fletcher Penney, who has put years of work into MultiMarkdown, has a new app: MultiMarkdown Converter Pro. If you write in Markdown or MultiMarkdown, this one is worth checking out. With MultiMarkdown Converter Pro, you can drag and drop text files from anywhere and convert them into the format you desire. It includes support for HTML5, EPUB 3 (including images), LaTeX, and Flat OpenDocument.
I'm a little late to this party but last week Brett Terpstra released version 2 of his Marked application. Marked is the last word in markdown preview on the Mac. I've already purchased mine and am using it.
Marked 2 tracks your file changes and updates the preview as you go, even automatically scrolling to the point in the file where you're currently working. The new version is faster and more accurate. I know there is a lot of work behind that speed improvement.
The application also supports MultiMarkdown 4.2 (including footnotes), better search, Fountain support, MarsEdit and system clipboard previews. You can also export to DOC, DOCX, ODT, RTF, RTFD, and paginated PDF. This is just a taste. Brett's gone crazy with great features. If you routinely write in Markdown, you'll have use for Marked 2. Get it from Brett directly.
I often hear from readers asking for an easy way to jump between markdown and Microsoft Word. It's never really been that easy. The most recent version of iA Writer takes a lot of work out of this problem. They have built in a converter that goes between docx files (Microsoft Word 2007 or later) and markdown. You can drag and drop the word file on the icon and it opens as a markdown file. Conversely you can export a markdown file from inside the application to docx.
Obviously there will be problems if you bring in multi column documents with advanced formatting outside the bounds of markdown. I tested it with a complicated document and it imported just fine but it did strip out some of the advanced formatting.
There's a lot to like about iA Writer and I'm glad to see they're continuing to innovate.
Yesterday was a great day for the MacSparky Field Guides. Markdown launched with a lot of success. I really enjoyed the twitter stream and feedback about the book. I particularly liked the tweets and email from people who always wanted to try Markdown and found this book the way to get them over the hump.
When Eddie and I first decided to do a book on Markdown, several nerd-friends told us we were nuts and that Markdown was such a niche topic that nobody would care. I think just the opposite. I think Markdown is a technology that needs to find its way to non-geeks and that's why we wrote the book.
At a deeper level, I enjoy writing and distributing these books so very much. In a lot of ways, it feels like the best work I've done of my lifetime. Thank you everyone for supporting me in this.
What's up next?
I am going to issue an update to Paperless. Several technologies and workflows have changed since the last update last September. You can expect that pretty soon.
As for the next big Field Guide, I've already got a big pile of words towards it and I'm looking forward to really digging in. The subject is another one of my personal crusades and I can't wait to share it with you. You'll probably see it sometime in the summer (hopefully early summer).
Thanks again everyone for supporting me on the MacSparky Field Guides.
Hey everybody, I just pushed the button on my newest MacSparky Field Guide.
I co-wrote this book with Eddie Smith and I'm really proud of it.
Markdown started as a clever way to write for the web but has become so much more. This book demystifies Markdown, making it easy for anybody to learn. This book includes 130 pages and 27 screencasts totaling more than one and a half hours of video. There is also an additional hour of audio interviews. This book will take you from zero knowledge of Markdown to being a Markdown pro and change the way you write for the better.
I've learned a great deal writing these Field Guides and I'm really happy with this book. Chapters include an explanation of why Markdown is important and why you should learn to write with it; full text and screencast walkthroughs of all the major components of Markdown (including cheat sheets), app and workflow recommendations for the Mac, PC, iPad, iPhone, and the web; advanced markdown techniques and tricks (including automation); and audio interviews with some of my favorite Markdown writers including Merlin Mann, Fletcher Penney, Brett Terpstra, Federico Viticci, and Gabe Weatherhead.
The book is built with iBooks Author and has all of the rich media you've come to expect from the MacSparky Field Guides. The book costs $10 and is available now in 51 countries and PDF. Get it while it's hot.
Learn more at the Markdown webpage.
I've made no secret of my admiration for Fletcher Penny, the renaissance physician behind MultiMarkdown. Fletcher just released version 2 of his successful MultiMarkdown Compser App for Mac. This is a substantial improvement over version 1 with upgrades to the underlying engine and most of its user interface. In other words, it got a new motor and a fancy new paint job. The app is just $5 for a limited time. In addition to getting yourself a great MultiMarkdown editor, you'll also be supporting Fletcher for all of the work he's done on MultiMarkdown. If you write in MultiMarkdown, go check it out.
Recently, I’ve switched my billing workflow in the day job over to markdown. As a result of the way I’m jumping between platforms, I’m not always getting proper markdown line breaks. (to force a
<br> code in markdown, you need to insert three spaces before hitting return.)
So I wrote my friend Brett Terpstra yesterday lamenting this hitch in my giddyup and Brett wrote back in ten minutes explaining: 1. This is solvable with a service; 2. He already solved it. Today you can download it with the latest update to Brett’s Markdown Services. These are so ridiculously useful. I ♥ Brett.
Fletcher Penney has been hard at work on MultiMarkdown 3.0. Perhaps one of the most inspired new features is the ability to work with OPML files. (Don’t know what OPML is? Read this.) Fletcher let me in on the secret early and it is absolutely nerd-tastic.
We are on the verge of something remarkable with our data. Simple data portability is here and it is killing the stranglehold of any one software developer over our digital toolbelts. This option-rich environment is letting people build their own workflows. For a change, the machines are working for us. How did we get here? I see a few reasons:
The Mobile Explosion
With the iPhone, iPad, and App store, Apple has turned the world of mobile computing on its head. Every step of the way, competitors laughed, then feared, then copied. People are digging these new multiple devices and, as a result, there are a lot of operating systems to play in.
Multiple Operating Systems
The whole Mac vs. PC thing arises from one dimension, desktop computing. Those days are over. There are now more operating systems than ever and people are no longer working in just one. I currently use three daily (four if you count the Web). Once the Tablet-aganza gets in full swing there will be even more options. People need to move their data between these operating systems. The text, markdown, and OPML standards are the foot soldiers used by every app to make this happen.
Home-Brew Apps, Inc.
An App stores supporting these new platforms create historical opportunities for small developers . Size doesn’t matter if you have a good idea and execute on it. These little guys are competing where only multi-million dollar companies dared a few years ago. The result is a rich environment of options where ten people can have their favorite App in any category and they are all different.
We finally have a way to easily sync files between computers, operating systems, and platforms. There is a reason everyone gets misty eyed when we talk about Dropbox: we remember how hard it used to be to sync. Now that syncing is easy, the data needs to work everywhere.
Just the Beginning
Us nerds are just figuring this all out. Things are only going to get easier and this speaks well for our future computing experiences. No longer will we all need to bend our habits to the foibles of a few applications. Instead we are going to pick the apps that work the way we think and move our data between them without a second thought. I can’t wait.
Brett is getting it together. His markdown snippets are more elegant than mine, which feel like the coding equivalent of Soviet-era public housing. Either way, I’m going to start pestering Brett to help out with this project and if you are a TextExpander/Markdown junkie, you should too.
This whole explosion of useful snippets resurrects an idea we kicked around at Macworld 2010. Why don’t we make a centralized depository for snippet bundles? There are a lot of nerds out there making some pretty fantastic snippets. Perhaps it is time we started sharing.
There is suddenly influx of Markdown and MultiMarkdown friendly apps on the iPad. While Markdown has provided an easy way to write for the web for years, the arrival of iOS devices and the need for portable text documents with retained formatting creates a perfect storm for widespread adoption of Markdown and MultiMarkdown for this purpose.
iOS developers have jumped on board with several interesting apps including MarkdownMail, Edito, and Elements. There are more. I’m still looking at these apps and making my own decisions about which ones I will incorporate into my workflows. This morning, I discovered a new contender, Trunk Notes (via Practically Efficient and Steven Frank) that allows you to create a Wiki synchronized through your Dropbox account (in an upcoming update) all for $1 (Through Monday). I waxed poetic about Markdown and MultiMarkdown in the upcoming Mac Power Users episode that will release this weekend. We even talked MultiMarkdown author Fletcher Penney to join us for a bit. Stay tuned.
Patrick Rhone (from MinimalMac) did his first screencast this week about creating a Text Expander snippet for Markdown links. Like Patrick, I write everything in Markdown (although I use the MultiMarkdown variant), which lets me export to nearly any format and write on the iPhone, iPad, and Mac without friction. I wrote the whole book in MultiMarkdown.*
Anyway, Patrick’s video got me thinking. Patrick puts his links right next to the linked words. I use Markdown’s reference links. The advantage of using referenced links is that the text is much easier to read. You can also use the same reference more than once. Reference links can be set anywhere in the document. Some folks do it at the end of the paragraph. I do them all at the bottom.
The syntax for reference links in Markdown works as follows:
First you type some [Link Text][Reference] Then more text … yadda yadda yadda [Reference]:Web URL
The Link Text is the text that shows up on the page. The Reference is an index. It can be a number or words. The Web URL is the link you are pointing toward. Here is concrete example.
This is one [nerdy Mac site.] Really, the guy just won’t shut up. :http://www.macsparky.com/
So I decided to take a page from Patrick’s playbook and create my own TextExpander snippet to create referenced links. It’s not that hard.
If you are thinking ahead while you write, you can do this all in one step. This snippet, upon activation, asks you to insert the Link Text and Reference and then creates a Reference entry on the next line using the Web link from your clipboard. Finally, it puts the cursor back at the end of your link text. Fire up TextExpander and follow along.
Create a new snippet and start with two sets of brackets. The first will hold the Link Text and the second will hold the Reference. The Snippet should now look like this:
— Begin Snippet Code —  — End Snippet Code —
Next, create a Fill-In blank for the Link Text. These are blanks that Text Expander will prompt you to fill when the snippet runs. To create a Fill-In blank, insert the cursor between the first two brackets and select Fill-In from the Cursor drop down shown below.
— Begin Snippet Code — [%fill:name%] — End Snippet Code —
Next, create a second Fill-In blank in the second set of brackets. This will be the blank for the Reference. When you create this second FIll-In blank, change the text from
fill:reference. This name is a variable. If you use the same name twice, TextExpander will copy it into both places. You will use this later.
— Begin Snippet Code — [%fill:name%][%fill:reference%] — End Snippet Code —
Next you’ll create the reference. First add a few carriage returns and then create the reference syntax, which is a pair of brackets and a colon.
— Begin Snippet Code — [%fill:name%][%fill:reference%] : — End Snippet Code —
Add a Fill-In blank in the brackets and rename it
fill:reference. This duplicates the reference used above so you only need to type it once.
— Begin Snippet Code — [%fill:name%][%fill:reference%] [%fill:reference%]: — End Snippet Code —
Next, add the Web URL. Place the cursor after the colon and select the Clipboard option from the cursor drop down shown in the figure below. This step dumps your clipboard in as a link. In order to make this work, you must first select and copy the link you want to use before activating the snippet. (You can do this in Safari by navigating to the desired page, pressing Command-L and then Command-C.) Alternatively, you could also make this a Fill-In field and type the URL in manually.
— Begin Snippet Code — [%fill:name%][%fill:reference%] [%fill:reference%]:%clipboard — End Snippet Code —
Finally, move the cursor back to the top line at the end of the link and select Position Cursor Here from the Cursor menu. This resets the cursor back in your text so you can continue typing.
— Begin Snippet Code — [%fill:name%][%fill:reference%] %| [%fill:reference%]:%clipboard — End Snippet Code —
I named this snippet Markdown Link and use the keyboard combination
.[ to set it off.
Here is a picture of it in action.
And here is the resulting code.
Link as Afterthought
The above workflow assumes you think of creating the link while you are typing. If you want to add a reference link later, I created two more snippets.
The first takes highlighted text in the body of your text and sets up the text and reference number. Here is the TextExpander snippet code. I use
.] to activate this snippet.
— Begin Snippet Code — [%clipboard][%fill:reference%] — End Snippet Code —
The second snippet creates the reference link. I use
.: for this one.
— Begin Snippet Code — [%fill:reference%]:%clipboard — End Snippet Code —
Are you a Markdown nerd and using TextExpander? Let me know or, better yet, leave a comment and describe it for everyone.
- I realize this post is putting the cart before the horse. I’ll be writing and speaking more about the how and why of MultiMarkdown soon. We are also planning a Mac Power Users episode around it. In the meantime, you can read John Gruber’s Markdown syntax guide, Fletcher Penny’s MultiMarkdown syntax guide, Practical Efficiency’s Markdown posts, and, of course, Patrick’s video.