For editing my markdown documents, I use the free MacDown, which gives a nice split screen, showing the raw markdown on the left and the interpreted version on the right.It's easy enough to do simple stuff this way, but getting to more complex documents requires some work. I was inspired by Dennis Tenen and Grant Wythoff's post last year, " Sustainable Authorship in Plain Text using Pandoc and Markdown," but I've long been a fan of avoiding proprietary formats that are likely to become obsolete (no doubt in part because I work with very old texts and materials professionally). The WorkflowI've started using markdown with pandoc to generate documents. I'll also link to it from my page (as well as here, obviously). Instead I'm going to post it as html on github and as a pdf on my account at figshare, where it's easily accessible, archived, and even gets a DOI. I could do it as a blog post, though it's already written in a more "academic" style than I write this blog in. (The advantages of tenure and the internet!) But since I don't go to such conferences, I figure I'll just put it out there for people to check out anyway. It's the kind of thing I'd do as a conference paper, if I went to a conference at which I think it'd be welcome. ![]() ![]() I'm not interested in doing more with it at this time, but it seems silly to have it just sit on my hard drive doing nothing. I sent it to a couple of OA journals, but neither wanted to publish it as is. ("Just done with" if you think that once commencement occurs, it's just a regular summer.) Among the things I produced in the past few months is a very short "note" on a topic that doesn't fall within my usual area of research. View My GitHub Profile 10 June 2015 Self-publishing with pandoc, etcĭepending on your thinking, I'm either just done with or approaching the end of a sabbatical.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |