I fancy myself a writer. Not, mind you, a good one. Just a passable one.
I am, however, definitively a programmer. This means that I like things like version control, scriptable or programmable tools, and open, easily interchangeable formats.
Currently, when I write things I write them in RTF or in ASCII with Markdown. I really like Markdown. I used to like RTF, until I realized that it has no really standard implementation. So I have resolved to move my writing away from RTF and into Markdown only.
So, ideally, here’s my writing setup:
- Any writing project is a git repository.
- All source files for the project are written in Markdown
- When a project is finished, an HTML version is produced using the python implementation of Markdown
- Additionally, when a project is finished, a PDF version is created with wkhtml2pdf
- Optionally, if I want to get designery, output files include some nice CSS, injected in either through a hack or some sort of nice templating tool (Jinja, anyone?).
It seems like a nice idea. Of course, the problem with it is that I have a bunch of stuff not produced in this fashion, and I need to convert it (mostly because I’m slightly OCD about having all my stuff in a similar state, but that is neither here nor there). Aaron Swartz has a nice tool called html2text, which works reasonably well as part of an RTF to HTML to Markdown conversion flow. The only problem now is that the Markdown produced doesn’t return to an entirely accurate final format.
I’ll continue on here about my experiments in this vein. In the meantime, other writers reading this: what is your setup, ideal or otherwise?
Those of us who refrained from referring to the administration you put into power Nazis would appreciate it if you, in turn, could avoid invoking 1984 at every action of the administration we put into power.
Thank you.
DZ commented on my previous post regarding an unfortunate use of an MLK quote.
There’s been a relatively unfortunate trend recently of idolizing the ridiculously obsessed. Obsessives, in some circles, equate automatically to quality and workmanship.
The problem here, I think, is that obsession becomes an easy stand in for meticulousness. It’s an understandable mistake to make, honestly. An artist or craftsman who is meticulous in the details of of their art or craft is generally obsessed; the focus of that obsession is however about something deeper than the number of icons on one’s desktop.
I don’t mean that a person’s obsessions are necessarily trivial—when John Gruber and Merlin Mann asked people to “pursue their obsessions in a serious way” I agreed with them along with most of the people in the world blogging. But to me, pursuing an obsession in a meaningful way means having some perspective.
Be meticulous in your pursuits—save obsession for the things that matter.
There’s a great little blog called Minimal Mac that has a wealth of nifty little tricks for computing happiness.
I’m not mentioning it because of one of these tricks. I’m mentioning it because just now it posted the following quote:
Our lives begin to end the day we become silent about things that matter.
That’s Martin Luther King, Jr.
Really? I mean, really?
I don’t know. Maybe MM was just sharing this b/c it’s a nice quote, but given the frequent posts it has regarding “what we believe in” and “not what we believe in” I’m left feeling as though it’s meant to be applied to their views on simple computing interfaces.
Thus: Really? Equating a matter of civil rights to decluttered desktops?