public inbox archive for pandoc-discuss@googlegroups.com
 help / color / mirror / Atom feed
From: John MACFARLANE <jgm-TVLZxgkOlNX2fBVCVOL8/A@public.gmane.org>
To: pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
Subject: Re: List items with custom markers in LaTeX
Date: Thu, 24 Aug 2017 11:26:01 -0700	[thread overview]
Message-ID: <20170824182601.GB74011@protagoras.berkeley.edu> (raw)
In-Reply-To: <00380dc8-ab11-44b7-bb1f-c9d37c182629-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>

I'd use a definition list, myself.

I wonder if it would make sense to generalize example lists
so that you could specify the marker instead of letting
it be determined automatically?

Then you could do

(@=P1). All men are mortal.
(@=P2). Socrates is a  man.
(@=C).  Socrates is mortal.

And then refer back later to premise (@P2).


+++ David Sanson [Aug 24 17 11:06 ]:
>   Does anyone have a filter or some other trick for producing lists with
>   custom markers? For example, I'd like to transform something like this:
>   P1.  All men are mortal.
>   P2. Socrates is a man.
>   C.  Socrates is mortal.
>   into an itemized list like this:
>   \begin{itemize}
>   \item[P1]
>   All men are mortal.
>   \item[P2]
>   Socrates is a man.
>   \item[C]
>   Scorates is mortal.
>   \end{itemize}
>   The best solution I've come up with is to format the list as a
>   definition list, convert it to LaTeX, and replace the definition
>   environment with the itemize environment. I suppose I could instead
>   redefine the definition list environment, but that seems a bit
>   heavy-handed.
>
>   --
>   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 [1]pandoc-discuss+unsubscribe-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org
>   To post to this group, send email to
>   [2]pandoc-discuss-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org
>   To view this discussion on the web visit
>   [3]https://groups.google.com/d/msgid/pandoc-discuss/00380dc8-ab11-44b7-
>   bb1f-c9d37c182629%40googlegroups.com.
>   For more options, visit [4]https://groups.google.com/d/optout.
>
>References
>
>   1. mailto:pandoc-discuss+unsubscribe-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
>   2. mailto:pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
>   3. https://groups.google.com/d/msgid/pandoc-discuss/00380dc8-ab11-44b7-bb1f-c9d37c182629-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org?utm_medium=email&utm_source=footer
>   4. https://groups.google.com/d/optout


  parent reply	other threads:[~2017-08-24 18:26 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-08-24 18:06 David Sanson
     [not found] ` <00380dc8-ab11-44b7-bb1f-c9d37c182629-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2017-08-24 18:26   ` John MACFARLANE [this message]
     [not found]     ` <20170824182601.GB74011-nFAEphtLEs/fysO+viCLMa55KtNWUUjk@public.gmane.org>
2017-08-29 15:40       ` David Sanson
     [not found]         ` <c89be225-fd55-410f-abd3-7c5f2108d061-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2017-08-29 16:14           ` John MacFarlane
     [not found]             ` <20170829161423.GA63436-9Rnp8PDaXcadBw3G0RLmbRFnWt+6NQIA@public.gmane.org>
2017-09-10 21:41               ` David Sanson

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=20170824182601.GB74011@protagoras.berkeley.edu \
    --to=jgm-tvlzxgkolnx2fbvcvol8/a@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).