public inbox archive for pandoc-discuss@googlegroups.com
 help / color / mirror / Atom feed
From: John MACFARLANE <jgm-TVLZxgkOlNX2fBVCVOL8/A@public.gmane.org>
To: pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
Subject: Re: Pandoc not maintaining newlines from .txt file to Word file
Date: Thu, 18 Jan 2018 12:25:29 -0800	[thread overview]
Message-ID: <20180118202529.GA59130@protagoras> (raw)
In-Reply-To: <e1d030fa-3ac1-4fb7-b6c8-3f7a29356d9a-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>

Try

-f markdown+hard_line_breaks

and the newlines in your document will be interpreted as
line breaks, if that's what you want.  (Don't include
raw '<br>' tags in the markdown; they will only be passed
on to HTML output, not docx.)

+++ Serena De Stefani [Jan 18 18 12:08 ]:
>   I am using Pandoc to integrate Scrivener with Zotero. I write in
>   Scrivener adding the Zotero citation keys, compile a .txt file, then
>   use Pandoc to convert the .txt file into a Word file in which the
>   citation keys are effectively translated in my preferred citation style
>   (APA in this case). Following the instructions on [1]this webpage, I
>   also set up "Marked 2" to show the output of what I was writing in
>   Scrivener using markdown.
>   Here comes the problem: newlines.
>   If I write in Scrivener:
>       I want a newline after this.
>       This should be a newline.
>   then Marked 2 is showing:
>       I want a newline after this. This should be a newline.
>   So then I wrote in Scrivener:
>       I want a newline after this.<br>
>       This should be a newline.
>   Marked 2:
>       I want a newline after this.
>       This should be a newline.
>   Great! Now I compile into a .txt file and I get:
>       I want a newline after this.<br>
>       This should be a newline.
>   OK, now it is time to use Pandoc.
>   I type the following command into the terminal:
>       pandoc -s -S --normalize --bibliography
>       ~/Dropbox/_Research/Master_Thesis/Master.bib --csl
>       ~/Dropbox/_Research/apa.csl
>       -f markdown -t docx -o trial.docx /Users/S/Desktop/test_st.txt
>   I get my .docx file (and when I do this with a full document, all my
>   citations are there, so that works!), but then I read:
>       I want a newline after this. This should be a newline.
>   Note that the <br> that was present in the .txt file is gone, but still
>   I did not get a newline.
>
>   --
>   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 [2]pandoc-discuss+unsubscribe-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org
>   To post to this group, send email to
>   [3]pandoc-discuss-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org
>   To view this discussion on the web visit
>   [4]https://groups.google.com/d/msgid/pandoc-discuss/e1d030fa-3ac1-4fb7-
>   b6c8-3f7a29356d9a%40googlegroups.com.
>   For more options, visit [5]https://groups.google.com/d/optout.
>
>References
>
>   1. https://davepwsmith.github.io/academic-scrivener-howto/
>   2. mailto:pandoc-discuss+unsubscribe-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
>   3. mailto:pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
>   4. https://groups.google.com/d/msgid/pandoc-discuss/e1d030fa-3ac1-4fb7-b6c8-3f7a29356d9a-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org?utm_medium=email&utm_source=footer
>   5. https://groups.google.com/d/optout


  parent reply	other threads:[~2018-01-18 20:25 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-01-18 20:08 Serena De Stefani
     [not found] ` <e1d030fa-3ac1-4fb7-b6c8-3f7a29356d9a-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2018-01-18 20:22   ` James AUSTIN
2018-01-18 20:25   ` John MACFARLANE [this message]
2018-01-18 20:30   ` Mikolaj Machowski
2018-01-18 22:32   ` Serena De Stefani

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=20180118202529.GA59130@protagoras \
    --to=jgm-tvlzxgkolnx2fbvcvol8/a@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).