![]() ![]() It's all up on github, so you can see what I've done. For html, I use a few different versions of my standard css file.(I was really hoping that I could generate my CV in html and PDF directly, since I've been maintaining html and odt versions, the latter of which I turned into PDF via OS X, but I've yet to get enough into LateX to be able to reproduce my mildly complicated CV format.) In most other cases, I don't need both html and odt/docx versions, so I can skip it there too. LateX PDFs have a certain look to them, but anything I can print, OS X can turn into a PDF, so that's not a big deal for me. ![]() There are just too many complications in academic documents (footnotes, etc) and my skills and time are limited. I'm mostly interested in html, OpenDoc, pdf and-sadly-Word. I've given up on using pandoc to produce final versions of the same file in different formats.Once this bibtex file is created, I can easily cite the works in it within markdown and then let pandoc-citeproc expand them as appropriate. I export it all as a a bibtex file using Better BibTeX, which provides some nice customization of the export entries. There are a number of pandoc "enhancements" to markdown that MacDown can't handle, but it gets the vast majority of the formatting right and it prevents me from making stupid mistakes in that majority. 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. |