![]() And being that it’s cleaner to read, if I want to switch to a different CSS file for different formatting, I can more quickly and easily modify the URL. Not exactly something I love to see at the top of all of my text files. To link my CSS file in a standard Markdown file, I can use the line: While Markdown is capable of using standard HTML code within the document, I much prefer the cleanliness and simplicity of the MultiMarkdown implementation.Įxample. The other huge advantage to using MultiMarkdown is the CSS metadata key. Of course I always have my iPhone with me and I can easily resend the PDF via Dropbox, but that takes longer than just emailing or texting a URL. Having that online backup saves my ass when I’m away from a computer and someone who has lost their copy needs to read my script ASAP. MultiMarkdown supports some great text to pdf conversion tools through LaTeX, but the simpler solution is simply to print to PDF directly from the browser preview.Īnother benefit of creating an HTML document from my text file is the ability to quickly upload it to my website and send a link to people. The second reason I user the browser for previewing is print support. ![]() First, let’s face it, any computer you sit down at these days is going to have at least one browser installed, and that’s just one less app I need to worry about installing for my workflow to function properly. Regardless of the operating system on the machine itself, I like the idea of doing my previewing in a browser for two reasons. But, unfortunately, I do the majority of my writing on a Windows 7 machine (please don’t email me ). Ideally to view the final document I’d use something like Brett Terpstra’s awesome Marked app. You may be asking, “But why does it need to be ready for the web? It’s a screenplay.” As much as I love writing in my text editor, eventually I will need to preview the final output of the properly formatted document. The metadata features give me a nice looking header to all my text files and, more importantly, creates a complete HTML document that’s ready for the web. If you don’t include metadata, then you will instead generate a “snippet.” The snippet will just include the relevant portion of HTML, but will not include the or elements. If you include metadata in your document (with two exceptions), then you will generate a complete document. The first reason is it’s inclusion of metadata and the ability to create a “complete document” rather than just an HTML “snippit”. There are a few reasons I chose to use MultiMarkdown instead of standard Markdown syntax. My solution is in no way as robust or polished as Stu’s SPMD proposal, but having used it for a few months now I find it suits my needs pretty well. ![]() After giving Stu way more input than he needed, I decided I wanted to use something like SPMD sooner rather than later.ĭue to my lack of any real programming skills, I decided the quickest way to get something usable was to continue writing in MultiMarkdown and use simple CSS to transform my output into something that looked like a screenplay. Back in August when Stu Maschwitz proposed Screenplay Markdown (formerly SPMD, now Fountain), I got very excited.
0 Comments
Leave a Reply. |