From: Serena De Stefani <serenadestefani-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: pandoc-discuss <pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
Subject: Re: Pandoc not maintaining newlines from .txt file to Word file
Date: Thu, 18 Jan 2018 14:32:45 -0800 (PST) [thread overview]
Message-ID: <43a87a2f-359d-4437-8ac5-57d444667a4e@googlegroups.com> (raw)
In-Reply-To: <e1d030fa-3ac1-4fb7-b6c8-3f7a29356d9a-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
[-- Attachment #1.1: Type: text/plain, Size: 2388 bytes --]
Thank you all for your help. I found that -f markdown+hard_line_breaks
worked!
On Thursday, January 18, 2018 at 3:08:38 PM UTC-5, Serena De Stefani wrote:
>
> 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 this
> <https://davepwsmith.github.io/academic-scrivener-howto/> 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 pandoc-discuss+unsubscribe-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org
To post to this group, send email to pandoc-discuss-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org
To view this discussion on the web visit https://groups.google.com/d/msgid/pandoc-discuss/43a87a2f-359d-4437-8ac5-57d444667a4e%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[-- Attachment #1.2: Type: text/html, Size: 3865 bytes --]
prev parent reply other threads:[~2018-01-18 22:32 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
2018-01-18 20:30 ` Mikolaj Machowski
2018-01-18 22:32 ` Serena De Stefani [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=43a87a2f-359d-4437-8ac5-57d444667a4e@googlegroups.com \
--to=serenadestefani-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).