public inbox archive for pandoc-discuss@googlegroups.com
 help / color / mirror / Atom feed
From: John MacFarlane <fiddlosopher-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
Subject: Re: blank lines get removed
Date: Thu, 23 Feb 2023 09:11:00 -0800	[thread overview]
Message-ID: <6463D128-E316-49BC-A312-7AB761D48162@gmail.com> (raw)
In-Reply-To: <001801d9479e$4017d990$c0478cb0$@blinksoft.com>

Try pandoc -f docx+empty_paragraphs

See manual under empty_paragraphs extension.

> On Feb 23, 2023, at 7:48 AM, <kperry-rhKcP+tiLR7by3iVrkZq2A@public.gmane.org> <kperry-rhKcP+tiLR7by3iVrkZq2A@public.gmane.org> wrote:
> 
>  
> We use pandoc to support different file types.  This means we do not control the files people import.   When I import a docx file pandoc seems to remove the blank lines. For example if I have a docx file that has the following in it
>  
> This is a line.
>  
> This is a second line
>  
>  
> This is a third line.
>  
> The two blank lines do not get represented if I output the native format.  Which makes me believe pandoc removes the blank lines. This is not good when trying to convert formatted documents.  Is there a option to pandoc that makes the blank lines not  be removed.
>  
> Ken
> 
> -- 
> 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/001801d9479e%244017d990%24c0478cb0%24%40blinksoft.com.

-- 
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/6463D128-E316-49BC-A312-7AB761D48162%40gmail.com.


  reply	other threads:[~2023-02-23 17:11 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-02-23 15:48 kperry-rhKcP+tiLR7by3iVrkZq2A
2023-02-23 17:11 ` John MacFarlane [this message]
     [not found]   ` <6463D128-E316-49BC-A312-7AB761D48162-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2023-02-23 17:29     ` kperry-rhKcP+tiLR7by3iVrkZq2A

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=6463D128-E316-49BC-A312-7AB761D48162@gmail.com \
    --to=fiddlosopher-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).