public inbox archive for pandoc-discuss@googlegroups.com
 help / color / mirror / Atom feed
From: Joseph Reagle <joseph.2011-T1oY19WcHSwdnm+yROfE0A@public.gmane.org>
To: pandoc-discuss <pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
Subject: Re: plain output, smart punctuation, and ascii
Date: Mon, 10 Jan 2022 09:31:54 -0500	[thread overview]
Message-ID: <f3d9e422-7e0c-a80d-eaa5-de4c6ecc94bd@reagle.org> (raw)
In-Reply-To: <m2lezrb25a.fsf-jF64zX8BO0+FqBokazbCQ6OPv3vYUT2dxr7GGTnW70NeoWH0uzbU5w@public.gmane.org>

On 22-01-07 17:40, John MacFarlane wrote:
> Remember, when the smart extension is applied to a *writer*, it
> means that straight quotes will be used.

Ah, thank you. I had read the documentation [1] but hadn't understood this. First, because "plain" isn't even listed as a possible output format, I wondered if that means there should be no change at all? Perhaps we should specify this is true of all output format, or all output text formats? And you do have the warning:

> Note: If you are writing Markdown, then the smart extension has the reverse effect: what would have been curly quotes comes out straight.

But this seemed the opposite of what you say above. In any case, I think specificity would help, such as saying "to=...+smart yields straight punctuation."

[1]: https://pandoc.org/MANUAL.html#extension-smart

   (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.
> 

-- 
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/f3d9e422-7e0c-a80d-eaa5-de4c6ecc94bd%40reagle.org.


      parent reply	other threads:[~2022-01-10 14:31 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
     [not found]     ` <m2lezrb25a.fsf-jF64zX8BO0+FqBokazbCQ6OPv3vYUT2dxr7GGTnW70NeoWH0uzbU5w@public.gmane.org>
2022-01-10 14:31       ` Joseph Reagle [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=f3d9e422-7e0c-a80d-eaa5-de4c6ecc94bd@reagle.org \
    --to=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).