public inbox archive for pandoc-discuss@googlegroups.com
 help / color / mirror / Atom feed
From: John MacFarlane <jgm-TVLZxgkOlNX2fBVCVOL8/A@public.gmane.org>
To: Don Raikes <DON.RAIKES-MouhYhfBpPxXrIkS9f7CXA@public.gmane.org>,
	pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
Subject: Re: Using fancy_lists
Date: Tue, 27 Aug 2019 12:16:17 -0700	[thread overview]
Message-ID: <yh480kftlmzaf2.fsf@johnmacfarlane.net> (raw)
In-Reply-To: <11acdbf7-7010-4389-b3df-c5682ae0232b@default>


fancy_lists is enabled by default for pandoc's markdown input,
so you don't need any special options, just '-f markdown'.

However, you should review the documentation for list nesting
with sublists.

Don Raikes <DON.RAIKES-MouhYhfBpPxXrIkS9f7CXA@public.gmane.org> writes:

> Hello,
>
>  
>
> I am new to pandoc (this week only), and I wish to create an outline for a project.
>
>  
>
> I want the outline to be of the standard type:
>
>  
>
> I.                  First topic
>
> a.      First sub-topic
>
> b.      Second sub-topic
>
>                                                     i.     First sub-sub-topic
>
>  
>
> II.                Second topic
>
> a.      First sub-topic
>
>  
>
> III.              etc
>
>  
>
> From the documentation, it looks like using fancy_lists extension is the way to do it, but I am unclear exactly how to:
>
>  
>
> Invoke the fancy_lists extension
>
> Actually create the outline list items.
>
>  
>
> Any tips / pointers / examples would be greatly appreciated.
>
>  
>
> BTW: I am writing in markdown and converting into docx if that makes any difference.
>
> -- 
> Thanks, Donald 
>
> Accessibility, like security, is better when built-in from the beginning rather than bolted on at the end.
>
>
> http://www.oracle.com/
> Donald Raikes | Accessibility Specialist
> Mobile: HYPERLINK "tel:+15202717608"+15202717608 | VOIP: HYPERLINK "tel:+15205744033"+15205744033 
> Oracle Accessibility Program Office
> | Tucson, Arizona 
>
> http://www.oracle.com/commitment
>
> Oracle is committed to developing practices and products that help protect the environment
>
>  
>
> -- 
> 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 view this discussion on the web visit https://groups.google.com/d/msgid/pandoc-discuss/11acdbf7-7010-4389-b3df-c5682ae0232b%40default.


  reply	other threads:[~2019-08-27 19:16 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-08-27 17:00 Don Raikes
2019-08-27 19:16 ` John MacFarlane [this message]
     [not found]   ` <yh480kftlmzaf2.fsf-pgq/RBwaQ+zq8tPRBa0AtqxOck334EZe@public.gmane.org>
2019-08-28 16:41     ` Don Raikes
2019-08-28 18:52       ` John MacFarlane
     [not found]         ` <yh480k4l21xguy.fsf-pgq/RBwaQ+zq8tPRBa0AtqxOck334EZe@public.gmane.org>
2019-08-28 19:23           ` Don Raikes
2019-08-29  0:51             ` John MacFarlane
     [not found]               ` <yh480kd0gox080.fsf-pgq/RBwaQ+zq8tPRBa0AtqxOck334EZe@public.gmane.org>
2019-08-29 16:01                 ` Don Raikes
2019-08-29 17:49                   ` John MacFarlane

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=yh480kftlmzaf2.fsf@johnmacfarlane.net \
    --to=jgm-tvlzxgkolnx2fbvcvol8/a@public.gmane.org \
    --cc=DON.RAIKES-MouhYhfBpPxXrIkS9f7CXA@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).