From: "philmac-97jfqw80gc6171pxa8y+qA@public.gmane.org" <philmac-97jfqw80gc6171pxa8y+qA@public.gmane.org>
To: pandoc-discuss <pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
Subject: How to change dumb quotes to smart quotes without converting formats?
Date: Mon, 18 Jul 2022 18:33:01 -0700 (PDT) [thread overview]
Message-ID: <defefcc0-b18e-4ffd-a188-472ee4a90963n@googlegroups.com> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 1074 bytes --]
I have text files written in Markdown, and I want to smarten their
punctuation. I know that, when *converting to* Markdown, Pandoc does this
by default with the smart extension
<https://pandoc.org/MANUAL.html#extension-smart>. Is there a way to apply
the effect of this extension to a file that is already in Markdown and that
I don't want to convert to some other format?
A wrinkle: I want to do this to all files in a directory, and I don't want
them text-wrapped. The command I'm presently using is:
for f in *.md; do pandoc --wrap=none "$f" -s -o "${f%.md}.md"; done
I guess it's no suprise that it doesn't do anything. I would appreciate any
help!
--
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/defefcc0-b18e-4ffd-a188-472ee4a90963n%40googlegroups.com.
[-- Attachment #1.2: Type: text/html, Size: 1451 bytes --]
next reply other threads:[~2022-07-19 1:33 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-19 1:33 philmac-97jfqw80gc6171pxa8y+qA [this message]
[not found] ` <defefcc0-b18e-4ffd-a188-472ee4a90963n-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2022-07-19 6:37 ` Bastien DUMONT
2022-07-19 16:24 ` PhilMac
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=defefcc0-b18e-4ffd-a188-472ee4a90963n@googlegroups.com \
--to=philmac-97jfqw80gc6171pxa8y+qa@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).