public inbox archive for pandoc-discuss@googlegroups.com
 help / color / mirror / Atom feed
From: John MacFarlane <jgm-TVLZxgkOlNX2fBVCVOL8/A@public.gmane.org>
To: Joseph Reagle
	<joseph.2011-T1oY19WcHSwdnm+yROfE0A@public.gmane.org>,
	pandoc-discuss
	<pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
Subject: Re: plain output, smart punctuation, and ascii
Date: Fri, 07 Jan 2022 14:40:33 -0800	[thread overview]
Message-ID: <m2lezrb25a.fsf@MacBook-Pro-2.hsd1.ca.comcast.net> (raw)
In-Reply-To: <385f2274-f83a-b837-0e82-de9c8245f0e3-T1oY19WcHSwdnm+yROfE0A@public.gmane.org>




Joseph Reagle <joseph.2011-T1oY19WcHSwdnm+yROfE0A@public.gmane.org> writes:

> I've noticed that when outputing to "plain," smart punctuation is used (including <0xa0> for non-breaking spaces). This seems counter to the docs and `--list-extensions=plain`.

Remember, when the smart extension is applied to a *writer*, it
means that straight quotes will be used.  (The idea is that
you're producing output that would be interpreted by something
with 'smart' support.)  When you disable smart, curly quotes
are used.  It's a bit counterintuitive but it makes sense when
you think about it.  (There's a recent thread on this list about
it.)

You can use `-t plain+smart` if you don't want this.


  parent reply	other threads:[~2022-01-07 22:40 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-07 21:39 Joseph Reagle
     [not found] ` <385f2274-f83a-b837-0e82-de9c8245f0e3-T1oY19WcHSwdnm+yROfE0A@public.gmane.org>
2022-01-07 22:40   ` John MacFarlane [this message]
     [not found]     ` <m2lezrb25a.fsf-jF64zX8BO0+FqBokazbCQ6OPv3vYUT2dxr7GGTnW70NeoWH0uzbU5w@public.gmane.org>
2022-01-10 14:31       ` Joseph Reagle

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=m2lezrb25a.fsf@MacBook-Pro-2.hsd1.ca.comcast.net \
    --to=jgm-tvlzxgkolnx2fbvcvol8/a@public.gmane.org \
    --cc=joseph.2011-T1oY19WcHSwdnm+yROfE0A@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).