From: John MacFarlane <jgm-TVLZxgkOlNX2fBVCVOL8/A@public.gmane.org>
To: Jean SALMON
<jean.salmon.orange-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>,
pandoc-discuss
<pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
Subject: Re: Keep Blank Lines between Docx To Gfm Markdown conversion ?
Date: Wed, 28 Aug 2019 09:37:11 -0700 [thread overview]
Message-ID: <m28srdcklk.fsf@johnmacfarlane.net> (raw)
In-Reply-To: <edc7c2a7-c9a7-4d9f-b89f-aaf3f74698b6-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
I'm not sure what you mean. Perhaps you could post a short
sample docx, the exact pandoc command you used, and what
you expected to get.
Jean SALMON <jean.salmon.orange-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> writes:
> Hi Eveybody.
>
> Thanks *hard_line_breaks* extension, foreach blank lines (only CR + LF),
> newlines are generating from a markdown file.
>
> pandoc -f markdown_github-hard_line_breaks
>
>
> Is it possible to do the same thing *from a Docx document* *to a Markdown
> file* ?
>
> Thanks for your help !
>
> Jean
>
> --
> 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/edc7c2a7-c9a7-4d9f-b89f-aaf3f74698b6%40googlegroups.com.
prev parent reply other threads:[~2019-08-28 16:37 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-28 8:27 Jean SALMON
[not found] ` <edc7c2a7-c9a7-4d9f-b89f-aaf3f74698b6-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2019-08-28 16:37 ` John MacFarlane [this message]
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=m28srdcklk.fsf@johnmacfarlane.net \
--to=jgm-tvlzxgkolnx2fbvcvol8/a@public.gmane.org \
--cc=jean.salmon.orange-Re5JQEeQqe8AvxtiuMwx3w@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).