From: John Kitchin <jkitchin@andrew.cmu.edu>
To: Marcin Borkowski <mbork@wmi.amu.edu.pl>
Cc: Org-mode mailing list <emacs-orgmode@gnu.org>
Subject: Re: Extending the Org syntax by a custom exporter - how to do it?
Date: Sat, 15 Mar 2014 07:10:31 -0400 [thread overview]
Message-ID: <CAJ51EToytVgSVof-POgb+ikKG2Zof8fsyx9B=ZZ-nvQ50nC1SQ@mail.gmail.com> (raw)
In-Reply-To: <20140315111059.00d3b8e0@aga-netbook>
[-- Attachment #1: Type: text/plain, Size: 2772 bytes --]
I suggest you look into the acrotex package (http://www.acrotex.net/) which
has good support for tests. You can use the regular latex exporter with
that.
John
-----------------------------------
John Kitchin
Associate Professor
Doherty Hall A207F
Department of Chemical Engineering
Carnegie Mellon University
Pittsburgh, PA 15213
412-268-7803
http://kitchingroup.cheme.cmu.edu
On Sat, Mar 15, 2014 at 6:10 AM, Marcin Borkowski <mbork@wmi.amu.edu.pl>wrote:
> Hi list,
>
> I'd like to extend the LaTeX exporter to be able to prepare tests with
> Org-mode. Four basic kinds of tests I'm thinking about are: single
> choice test, multiple choice test, cloze test and an "open" question
> (where the expected answer is, say, at most 5 lines of text). It
> would enable the user to typeset both the test for students and an
> answer sheet for the teacher to facilitate grading. (If - and when - I
> succeed in doing this, next logical step is preparing HTML/Javascript
> tests from the same Org-mode source.) I have a few questions, though.
>
> 1. Is it possible to employ syntax like ____{noon|midday} to denote a
> cloze with two possible answers? It might get translated to LaTeX as
> e.g. \cloze{{noon},{midday}} or similar, and a LaTeX package would
> take care to typeset this correctly. Is there any similar thing (i.e.,
> an exporter built on some existing one) so that I can look at an
> example of code doing such thing?
>
> 2. What would you suggest as the input format on the Org side of
> things? My suggestion for the cloze syntax is shown above (let us
> assume that at least two or three underscores are needed to
> distinguish this from subscript, and some form of escaping the pipe
> symbol and braces might be necessary. Alternatively, it might be
> configurable to use e.g. ____[noon/midday] (or other characters).
>
> What about SCTs/MCTs? My idea would be to employ plain lists with
> checkboxes - they seem to be pretty useless outside Org-mode anyway,
> and I imagine that it could be something like this:
>
> #+<SOME MAGICAL LINE MEANING: THIS IS A MULTIPLE CHOICE TEST>
> - [ ] wrong answer
> - [X] good answer
> - [X] another good answer
> - [ ] a completely stupid answer
>
> As for "open" questions, I have no good idea. Maybe something like
>
> #+LINES: 5
>
> but what about example answers (for the teacher grading the test)?
> Maybe it would be better to say:
> #+BEGIN_ANSWER
> (Here goes the right answer.)
> #+END_ANSWER,
>
> but is it possible to pass a parameter (number of lines) to
> #+BEGIN_ANSWER?
>
> 3. Bonus question: would there be any demand (apart from myself) for
> such an exporter?
>
> What do you think?
>
> --
> Marcin Borkowski
> http://octd.wmi.amu.edu.pl/en/Marcin_Borkowski
> Adam Mickiewicz University
>
>
[-- Attachment #2: Type: text/html, Size: 3596 bytes --]
next prev parent reply other threads:[~2014-03-15 11:10 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-15 10:10 Extending the Org syntax by a custom exporter - how to do it? Marcin Borkowski
2014-03-15 11:10 ` John Kitchin [this message]
2014-03-15 11:25 ` Marcin Borkowski
2014-03-15 11:29 ` Marcin Borkowski
2014-03-15 21:22 ` Marcin Borkowski
2014-03-16 10:16 ` Nicolas Goaziou
2014-03-16 11:18 ` Marcin Borkowski
2014-03-16 11:57 ` Nicolas Goaziou
2014-03-16 13:33 ` Marcin Borkowski
2014-03-16 14:12 ` Nicolas Goaziou
2014-03-17 15:43 ` Marcin Borkowski
2014-03-16 16:05 ` Aaron Ecay
2014-03-17 16:31 ` Marcin Borkowski
2014-03-22 11:23 ` Nicolas Goaziou
2014-11-25 21:25 ` Marcin Borkowski
2014-11-25 21:46 ` Marcin Borkowski
2014-11-26 2:46 ` John Kitchin
2014-11-26 14:23 ` John Kitchin
2014-11-26 11:59 ` Nicolas Goaziou
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
List information: https://www.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAJ51EToytVgSVof-POgb+ikKG2Zof8fsyx9B=ZZ-nvQ50nC1SQ@mail.gmail.com' \
--to=jkitchin@andrew.cmu.edu \
--cc=emacs-orgmode@gnu.org \
--cc=mbork@wmi.amu.edu.pl \
/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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).