From: "siliconvalley58-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org" <siliconvalley58-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org,
John MacFarlane <jgm-TVLZxgkOlNX2fBVCVOL8/A@public.gmane.org>
Subject: Re: Smart seems not the same of --smart
Date: Mon, 11 Dec 2017 10:36:24 +0100 [thread overview]
Message-ID: <385b120d-0fa4-e68b-084b-05b736477c53@gmail.com> (raw)
In-Reply-To: <20171210183631.GB600-9Rnp8PDaXcadBw3G0RLmbRFnWt+6NQIA@public.gmane.org>
Now understand. Thanks!
Seems mine is a misplaced expectation.
Could I promote the issue to feature request?
Something like an extension called force-smart that converts every quote
and every ... to the typographic form.
It is quite common for me to find non-typographic sign in Word documents
due to pasting a plain text to Word.
Thanks again
mario
On 10-Dec-17 19:36, John MacFarlane wrote:
> +smart doesn't affect the docx reader at all. Jesse
> Rosenthal might be able to say more about this decision, but
> I imagine it's because Word already has a smart quote
> feature, converting straight to curly quotes on the fly, so
> the assumption is that straight quotes are there because
> they're wanted (like an escaped \" in markdown).
>
> +++ Mario Valle [Dec 09 17 19:42 ]:
>> smart works going in the other direction from markdown to docx:
>> pandoc -f markdown+smart -o ex2.docx ex.md
>> Besides devising a monster pipeline (docx -> md | md+smart -> docx |
>> docx -> md-smart)
>> is there other ways to convert normal to smart quotes?
>> Thanks for looking!
>> 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 [1]pandoc-discuss+unsubscribe-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org
>> To post to this group, send email to
>> [2]pandoc-discuss-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org
>> To view this discussion on the web visit
>> [3]https://groups.google.com/d/msgid/pandoc-discuss/6936cf4f-665b-47e6-
>> 8895-4efaa226709b%40googlegroups.com.
>> For more options, visit [4]https://groups.google.com/d/optout.
>>
>> References
>>
>> 1. mailto:pandoc-discuss+unsubscribe-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
>> 2. mailto:pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
>> 3.
>> https://groups.google.com/d/msgid/pandoc-discuss/6936cf4f-665b-47e6-8895-4efaa226709b-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org?utm_medium=email&utm_source=footer
>> 4. https://groups.google.com/d/optout
>
--
Ing. Mario Valle
Swiss National Supercomputing Centre (CSCS)
v. Trevano 131, 6900 Lugano, Switzerland
Tel: +41 (91) 610.82.60
--
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/385b120d-0fa4-e68b-084b-05b736477c53%40gmail.com.
For more options, visit https://groups.google.com/d/optout.
next prev parent reply other threads:[~2017-12-11 9:36 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-09 18:15 Mario Valle
[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 [this message]
[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=385b120d-0fa4-e68b-084b-05b736477c53@gmail.com \
--to=siliconvalley58-re5jqeeqqe8avxtiumwx3w@public.gmane.org \
--cc=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).