From: Mario Valle <siliconvalley58-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: pandoc-discuss <pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
Subject: Smart seems not the same of --smart
Date: Sat, 9 Dec 2017 10:15:50 -0800 (PST) [thread overview]
Message-ID: <3b130b4c-1993-468b-b605-23bc04c8bc16@googlegroups.com> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 1407 bytes --]
In 1.19.2.1 I was using --smart in the conversion from docx to markdown.
Now with 2.0.4 I don't know how to use the smart extension to have the same
effect, that is, to convert normal quotes into smart ones. Here is my
command line:
pandoc -f docx --atx-headers --wrap=none --extract-media=. -t markdown
MyFile.docx
The input docx file contains normal quotes and three dots from a paste of a
text file (example attached). It contains also normal smart quotes
introduced by Word.
if I use -t markdown-smart everything remains as is in the docx file.
Instead using -t markdown or -t markdown+smart , as documented, changes
"aa" to \"aa\" and smart quotes to normal quotes. Also, as documented,
adding +smart to docx has no effect.
Can someone enlighten me how to ask pandoc to change normal quotes to smart
ones?
Thanks!
mario
--
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/3b130b4c-1993-468b-b605-23bc04c8bc16%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[-- Attachment #1.2: Type: text/html, Size: 3003 bytes --]
[-- Attachment #2: ex.docx --]
[-- Type: application/vnd.openxmlformats-officedocument.wordprocessingml.document, Size: 12450 bytes --]
next reply other threads:[~2017-12-09 18:15 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-09 18:15 Mario Valle [this message]
[not found] ` <3b130b4c-1993-468b-b605-23bc04c8bc16-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2017-12-10 3:42 ` Mario Valle
[not found] ` <6936cf4f-665b-47e6-8895-4efaa226709b-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2017-12-10 18:36 ` John MacFarlane
[not found] ` <20171210183631.GB600-9Rnp8PDaXcadBw3G0RLmbRFnWt+6NQIA@public.gmane.org>
2017-12-11 9:36 ` siliconvalley58-Re5JQEeQqe8AvxtiuMwx3w
[not found] ` <385b120d-0fa4-e68b-084b-05b736477c53-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2017-12-11 15:37 ` John MacFarlane
2017-12-12 9:36 ` BP Jonsson
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=3b130b4c-1993-468b-b605-23bc04c8bc16@googlegroups.com \
--to=siliconvalley58-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).