Pandoc
161–170 of 213 posts
Re: Pandoc
#162I do all of my academic writing in pandoc. As compared to LaTeX this means no boilerplate (yet you can still use full LaTeX syntax for equations and the like) and, if the publisher 'needs' a Word file, you are one click away from providing it. All with plain text files that you can put under version control, get meaningful diffs, etc. It's just great.
Once the work has moved into a Word file, isn't that where it stays? Editors and publishers often make heavy use of features like track changes and notes. Doesn't pandoc lose that information?
Re: Pandoc
#163Re: Pandoc
#164I know it's well intended and somewhat successful, but I can't help but thinking of xkcd.com/927 Sorry, I couldn't resist.
It's a conversion tool for existing formats.
Re: Pandoc
#165Earlier quoted context omitted.
The paper "GADTs Meet Their Match" (first I had in my list) seems to work fine, but I don't know what it was generated with.
I'll pick on one of my own random papers: https://www.cs.york.ac.uk/aig/projects/implied/docs/cp03.pdf Try extracting "Theorem 2" on page 5, or any text really. I just get random noise through either a PDF reader, or something like pdf2ascii / ps2ascii. We just made this with standard latex.
I work with course materials made in Latex, and students sometimes need/want to copy and paste from them, so I try to avoid these kinds of problems.
Re: Pandoc
#166Earlier quoted context omitted.
LaTeX editors have simple keybindings for this, like ctl-b., or C-c C-f C-b in emacs, which makes this kind of thing a non-issue for me...
Just reading C-c C-f C-b is an issue for me and I haven't even tried to remember and type it yet.
Re: Pandoc
#167I wrote a little utility that uses Pandoc to read Markdown files like `man` pages in the terminal: https://github.com/ashton314/marked-man It's just a one-liner: `pandoc -s -t man "$1" | groff -T utf8 -man | $PAGER` (That was basically stolen from an answer to one of my questions on Stack Overflow—thanks to those who answered! :)
Re: Pandoc
#168Occasional pandoc contributor here, AMA :-) Just a few links: - Where everything is documented: http://pandoc.org/MANUAL.html - If you have questions or suggestions: https://groups.google.com/forum/#!forum/pandoc-discuss - Contributing to pandoc is also a great way to get your feet wet with Haskell. In my experience, very supportive community. See http://pandoc.org/CONTRIBUTING.html and for good first issues: https:/…
everytime I see a project using google groups, i think it is already dead. Gladly yours seems to be used quite often. At least you can search it even years later, compared to an irc or slack channel.
Re: Pandoc
#169I do all of my academic writing in pandoc. As compared to LaTeX this means no boilerplate (yet you can still use full LaTeX syntax for equations and the like) and, if the publisher 'needs' a Word file, you are one click away from providing it. All with plain text files that you can put under version control, get meaningful diffs, etc. It's just great.
> if the publisher 'needs' a Word file, you are one click away from providing it Once the work has moved into a Word file, isn't that where it stays? Editors and publishers often make heavy use of features like track changes and notes . Doesn't pandoc lose that information?
Re: Pandoc
#170Earlier quoted context omitted.
"Soon the structure underlying The Da Vinci Code and Angels and Demons and The Lost Symbol was laying bare before my eyes. I could see why the stories worked. I had reverse-engineered Dan Brown." Could you talk a little more in depth about what Dan Brown's pattern/structure is?
I get that request a lot, so I'll have to write something about it :) All I can offer right now is my raw notes, which are in Spanish. This is a structural analysis of Angels and Demons, The da Vinci Code, and The Lost Symbol: https://imgur.com/bX6ByJA This is an one-page treatment of the three books, with the "blanks" filled appropriately for each: https://imgur.com/LlDVUKn I doubt any of this is groundbreaking. Sto…