From: John Muccigrosso <jmuccigr-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: pandoc-discuss <pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
Subject: Re: NYC DH Week
Date: Mon, 9 Jan 2017 10:12:36 -0800 (PST) [thread overview]
Message-ID: <0f45a959-6d8b-4fa6-bc9e-541cd62976b0@googlegroups.com> (raw)
In-Reply-To: <890F613E-F940-4468-A73C-326CA07C479E-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
[-- Attachment #1.1: Type: text/plain, Size: 2793 bytes --]
On Saturday, January 7, 2017 at 7:45:39 AM UTC-5, Scot Mcphee wrote:
>
>
> On 06 Jan 2017, at 05:07 , John Muccigrosso <jmuc...-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org
> <javascript:>> wrote:
>
> pandockers,
>
> (Thought I might have coined a phrase, but I see it's been used a couple
> of times. @jgm, you should ™ that.)
>
> I just found out that I'm doing a workshop at the NYC DH week in a month
> (Feb 9, 1-3pm, to be precise). I've called it "Making the most of text:
> Using a text-only workflow with markdown and pandoc".
>
> Any suggestions/tips gratefully appreciated.
>
>
> Hi John
>
> What sort of suggestions were you after. I do quite a lot of DH in
> Classics on the programming side, but my thesis (which is not DH-based, but
> straight classics/ancient history) is fully written in pandoc style
> markdown. Classics has been using digital tools a lot longer than most
> other humanities disciplines (witness Perseus), because of its long
> relationship with philology, linguistics, and use of tools like
> concordances.
>
> Whenever I strike my fellow postgrads struggling with Word issues, I keep
> telling people to use markdown to write their thesis in markdown. They
> freak out. They think it’s difficult, when a thesis document nearly all
> text and simple to write in markdown. Our systems pretty much train them in
> undergraduate courses to use Word and never let up from that point.
>
> Scot.
>
> --
> Scot Mcphee
> Computer Programmer, Classics PhD.
> p +61 412 957414
> e scot....-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org <javascript:>
> w http://autonomous.org/
> <http://www.google.com/url?q=http%3A%2F%2Fautonomous.org%2F&sa=D&sntz=1&usg=AFQjCNEzdj0qs9dNerErHk6s2pPFXLNSAQ>
> t @scotartt
>
Scott,
I'm looking for whatever people have found useful when introducing the
concept of a text-only workflow to academics, and then adding the pandoc
icing on the cake.
So it's wide open. :-)
I expect most people to be beginners or even completely new to the idea,
though they will sign up for the workshop and so be self-selected, which
should mean that they are at least open to the idea.
So fire away.
--
You received this message because you are subscribed to the Google Groups "pandoc-discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email to pandoc-discuss+unsubscribe-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org
To post to this group, send email to pandoc-discuss-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org
To view this discussion on the web visit https://groups.google.com/d/msgid/pandoc-discuss/0f45a959-6d8b-4fa6-bc9e-541cd62976b0%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[-- Attachment #1.2: Type: text/html, Size: 4649 bytes --]
next prev parent reply other threads:[~2017-01-09 18:12 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-05 19:07 John Muccigrosso
[not found] ` <f48ee0d0-45bb-4d1b-8632-5a9817a10e6b-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2017-01-05 20:51 ` Fernando Botelho
2017-01-05 21:23 ` Albert Krewinkel
2017-01-06 2:10 ` John Muccigrosso
[not found] ` <70b111ff-2afd-4d57-a0bf-954381198e5b-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2017-01-06 8:57 ` BPJ
2017-01-07 12:45 ` Scot Mcphee
[not found] ` <890F613E-F940-4468-A73C-326CA07C479E-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2017-01-09 18:12 ` John Muccigrosso [this message]
[not found] ` <0f45a959-6d8b-4fa6-bc9e-541cd62976b0-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2017-01-11 11:58 ` Scot Mcphee
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=0f45a959-6d8b-4fa6-bc9e-541cd62976b0@googlegroups.com \
--to=jmuccigr-re5jqeeqqe8avxtiumwx3w@public.gmane.org \
--cc=pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).