public inbox archive for pandoc-discuss@googlegroups.com
 help / color / mirror / Atom feed
From: "'Nikolay Mihaylov' via pandoc-discuss" <pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
To: pandoc-discuss <pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
Subject: Re: When Converting From DOCX to Markdown Formatting For Lists Are Not Carried Over
Date: Mon, 16 May 2022 23:51:27 -0700 (PDT)	[thread overview]
Message-ID: <a59d216d-f527-4d14-a9b8-f75da3f1af19n@googlegroups.com> (raw)
In-Reply-To: <e575a611-a1ba-4875-8c92-4f41aea7dff1n-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>


[-- Attachment #1.1: Type: text/plain, Size: 779 bytes --]

You should use `-t gfm` flag for bullet lists to work. 

On Sunday, May 15, 2022 at 1:29:36 AM UTC+3 kfje...-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org wrote:

> Why is it that when I convert from Docx to Markdown, bulleted and numbered 
> lists do not retain formatting i.e., no "-" in front of each unordered list 
> item, and no number in front of each numbered item.

-- 
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/a59d216d-f527-4d14-a9b8-f75da3f1af19n%40googlegroups.com.

[-- Attachment #1.2: Type: text/html, Size: 1296 bytes --]

  parent reply	other threads:[~2022-05-17  6:51 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-14 22:29 Kevin Fjelsted
     [not found] ` <e575a611-a1ba-4875-8c92-4f41aea7dff1n-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2022-05-17  6:51   ` 'Nikolay Mihaylov' via pandoc-discuss [this message]
     [not found]     ` <a59d216d-f527-4d14-a9b8-f75da3f1af19n-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2022-05-17 10:19       ` Kevin Fjelsted
     [not found]         ` <6F48F869-C199-4EE6-9050-278CF14C78EC-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2022-05-17 10:43           ` Bastien DUMONT
2022-05-17 22:58             ` Kevin Fjelsted
     [not found]               ` <662275E5-EDA3-4D1D-B8C2-51B4EA12C103-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2022-05-18  6:44                 ` Bastien DUMONT
2022-05-18 14:30                   ` Kevin Fjelsted
     [not found]                     ` <06C4B1E7-54D0-44D9-98B0-D47AB6A0CB21-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2022-05-18 15:45                       ` Bastien DUMONT
2022-05-18 17:57                         ` Kevin Fjelsted
     [not found]                           ` <502CBF2E-C516-4E63-97A5-38DFC6CB22D9-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2022-05-18 18:44                             ` BPJ
2022-05-18 18:02                         ` Kevin Fjelsted
     [not found]                           ` <3EC245C1-7D01-4B78-A445-DB215285A29D-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2022-05-18 21:20                             ` Kevin Fjelsted
     [not found]                               ` <07CD1F5A-8D33-419E-AF1A-25107C02C360-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2022-05-18 23:25                                 ` Bastien DUMONT

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=a59d216d-f527-4d14-a9b8-f75da3f1af19n@googlegroups.com \
    --to=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).