public inbox archive for pandoc-discuss@googlegroups.com
 help / color / mirror / Atom feed
From: Don Raikes <DON.RAIKES-MouhYhfBpPxXrIkS9f7CXA@public.gmane.org>
To: pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
Subject: RE: Using fancy_lists
Date: Thu, 29 Aug 2019 09:01:10 -0700 (PDT)	[thread overview]
Message-ID: <d04583f4-68eb-474e-99c7-006bdc52d8de@default> (raw)
In-Reply-To: <yh480kd0gox080.fsf-pgq/RBwaQ+zq8tPRBa0AtqxOck334EZe@public.gmane.org>

I am running pandoc 2.7.3 on windows 10.

I also have access to an installation of pandoc 2.2.1 on debian buster. 2.2.1 seems to be the latest release of pandoc in the repositories.
-----Original Message-----
From: John MacFarlane <jgm-TVLZxgkOlNX2fBVCVOL8/A@public.gmane.org> 
Sent: Wednesday, August 28, 2019 5:52 PM
To: Don Raikes <don.raikes-QHcLZuEGTsvQT0dZR+AlfA@public.gmane.org>; pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
Subject: RE: Using fancy_lists

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

> Yes if I use just regular list markup, converting it to docx does create regular lists, but with the fancy_list format it is not being presented as a listin the docx file.

That's strange. It works perfectly for me.
Have you said what version of pandoc you have?


  parent reply	other threads:[~2019-08-29 16:01 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
     [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 [this message]
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=d04583f4-68eb-474e-99c7-006bdc52d8de@default \
    --to=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).