![plain text workflow plain text workflow](https://4.bp.blogspot.com/-zN-FvFzbzpk/U-o4TpcSjdI/AAAAAAAABIU/aJjLGnbtF5Y/s1600/pic01_WorkflowSetup.gif)
- #Plain text workflow pdf
- #Plain text workflow pro
- #Plain text workflow software
- #Plain text workflow code
#Plain text workflow pdf
It’s readily convertible to MSWord format, as well as PDF (if you’ve installed LaTeX), HTML, and all kinds of more arcane things-it’s very commonly used by programmers and bloggers, and I think it’s by far the best way to write initial drafts. Markdown, for those who aren’t familiar, is a plain text format with very lightweight markup for things like bold/italics, links, and the like. So my workflow has the following elements: I want to use git for version control so that I can recover prior versions if something gets horribly screwed up. I like being able to relatively seamlessly switch between writing on my MacBook and on my iPad.Į. I also hate manually formatting my citations.ĭ. Most of the major alternatives to word (OpenOffice, Google Docs, Pages) are crap.Ĭ. Word “features” like styled paste, auto-conversion of URLS to links, bizarre dictatorial bullet point numbering, etc. I also want something that doesn’t impose involuntary formatting on me.
#Plain text workflow code
My writing needs to be scriptable-I need to be able to read my writing into an ordinary programming language as a string, run code on it, and spit it back out again as a string. If I want to do something weird or automated with my content, I want to be able to do so. It takes longer to start than XCODE, which, for those of you who program, you’re probably screaming in horror at the very idea.)
#Plain text workflow pro
I have a brand new souped up 16-inch Macbook Pro with an i9 and 32 gigs of ram. (It’s utterly mind-blowing how badly Word performs. I want something that doesn’t crash or hang all the time, unlike Word. Yet I recognize that many people that publish things I write need Word format, so I need to do something that converts to Word fairly readily. Subconsiderations: I won’t use it if it can be helped at all. I’m incredibly paranoid about losing work.ī.
![plain text workflow plain text workflow](https://zenaton.com/uploads/screenshot-2020-02-19-15.33.31.png)
![plain text workflow plain text workflow](https://help.smartsheet.com/sites/default/files/inline-images/Triggers%20using%20Phrases.png)
Here are the considerations, in rough order of priority, that drive me:Ī. This is a work in progress document I’ve promised to share my toolkit with a couple people, so, as those people say to me “hey, this makes no sense,” I’ll probably edit to clarify. I have an unusual and complicated academic writing workflow/toolkit, but one that might be of use to some other people, so I thought I’d share it here. I recommend slightly modifying the pandoc command referenced in the article to guarantee proper formatting (this will make sense once you’ve read their piece): pandoc main.md -f markdown-smart -filter pandoc-citeproc -o main.This one is for academics rather than practitioners, though some of the details are applicable to practitioners as well.
#Plain text workflow software
Taking the step to disable AutoCorrect is a good preliminary move, but what happens when the software updates and settings are reverted to their defaults without you knowing about it? Tenen and Wythoff describe a viable alternative – in their words, a more ‘sustainable’ solution – and it’s well worth a read. The problem is all the more urgent for anyone who works directly with original manuscript material: even something as subtle as a wrongly formatted space, punctuation mark, or capital letter can completely undermine the accuracy of your transcription, creating headaches when you return to your work and wish to rely upon it later. Any pre-modern language looks like a protracted typo to these programs, and they will constantly fight you in your attempt to write them out accurately. The most commonly used technologies in humanities scholarship today (Microsoft Word, PowerPoint, etc.) constantly intervene in your writing in order to ‘help’ you write correctly. Tenen and Wythoff address a general scholarly audience, but this article can be of particular use to medievalists. I wanted to share a piece by Dennis Tenen and Grant Wythoff that has completely changed the way I think about conducting research in the humanities: Sustainable Authorship in Plain Text using Pandoc and Markdown.