public inbox archive for pandoc-discuss@googlegroups.com
 help / color / mirror / Atom feed
From: Rik <amphiboly-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
Subject: Re: Citeproc is bringing a question mark inside quotes?
Date: Fri, 25 Jun 2021 17:24:58 -0400	[thread overview]
Message-ID: <sb5hjc$ene$1@ciao.gmane.io> (raw)
In-Reply-To: <b35ebef4-358f-4542-8dda-d68a7c1ab3fan-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>

On 6/25/2021 13:47, gnpan wrote:
> This is a csl locale issue, US is default. You can try --metadata 
> lang=en-GB as suggested here 
> <https://github.com/jgm/pandoc/issues/7005> or add a zero-width-space as 
> mentioned here 
> <https://groups.google.com/g/pandoc-discuss/c/NiFPVF9TeCg/m/9pHluL3iAgAJ>.
> 
> 
> On Friday, 25 June 2021 at 14:38:07 UTC+3 William Lupton wrote:
> 
>     Hello,
> 
>     It seems that adding --citeproc causes a question mark to be brought
>     within quotes, which I didn't expect. I tried escaping it but this
>     didn't make any difference. Putting a space before it avoids the
>     behaviour... but I don't want a space!
> 
>     Thanks,
>     William
> 
>     % pandoc -v
>     pandoc 2.14.0.3
> 
>     % cat question.md
>     '-'?
> 
>     % pandoc question.md
>     <p>‘-’?</p>
> 
>     % pandoc --citeproc question.md
>     <p>‘-?’</p>
> 


US practice is to put commas and stops inside the quotation marks of a 
quotation and larger punctuation (?!;:) outside, except in the case that 
the large punctuation is part of the quoted material (“Who, me?”). So, 
US practice supports both.
   Similarly, British (or UK, or GB) practice places marks in a default 
position (outside) but allows them inside based on the semantic content.
   If CSL US locale processing is mangling this by moving both large and 
small marks in every case, then CSL processing is creating some new 
standard. I would suggest that if the proper position cannot be 
programmatically determined it should default to what the writer writes.
   Quotation marks are used for other things than quotations. Indeed, 
the use in citation processing is such another use. Again the writer 
must be trusted to place punctuation properly in context. A.J. Liebling 
wrote ‘Do You Belong in Journalism?’ in 1960; did he write it in his 
regular column ‘The Wayward Press’?
   The behavior identified here takes place outside of citation 
processing. The OP is rightly surprised that it results in changes 
beyond that scope.

-- 
Rik

-- 
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/sb5hjc%24ene%241%40ciao.gmane.io.


  parent reply	other threads:[~2021-06-25 21:24 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-06-25 11:37 William Lupton
     [not found] ` <CAEe_xxjq6BMv2UuxKQUdM3JcKReup8XPnwpG_TV-22SqqZ0tXQ-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2021-06-25 11:47   ` William Lupton
2021-06-25 17:47   ` gnpan
     [not found]     ` <b35ebef4-358f-4542-8dda-d68a7c1ab3fan-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2021-06-25 19:55       ` William Lupton
     [not found]         ` <CAEe_xxhEX0Tev22__+TO7Ksy9=5j53=ZNoq8MWeHXnc2KfE7nA-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2021-06-25 20:00           ` William Lupton
2021-06-25 21:24       ` Rik [this message]
2021-06-26  6:18         ` gnpan
     [not found]           ` <33940371-e6ec-4176-9483-8f06ec1b75ecn-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2021-06-26  6:21             ` gnpan
2021-06-28 17:22   ` John MacFarlane
     [not found]     ` <m2eeclnbu5.fsf-jF64zX8BO0+FqBokazbCQ6OPv3vYUT2dxr7GGTnW70NeoWH0uzbU5w@public.gmane.org>
2021-06-28 18:57       ` AW: " denis.maier-NSENcxR/0n0
     [not found]         ` <1b63b1d8bacf454e9db84a056d06a00f-NSENcxR/0n0@public.gmane.org>
2021-06-28 22:59           ` John MacFarlane
     [not found]             ` <m2r1gllhn7.fsf-jF64zX8BO0+FqBokazbCQ6OPv3vYUT2dxr7GGTnW70NeoWH0uzbU5w@public.gmane.org>
2021-06-29  8:46               ` AW: " denis.maier-NSENcxR/0n0
     [not found]                 ` <ad9e052a2cb84bb2a203ca3eaea55dd1-NSENcxR/0n0@public.gmane.org>
2021-06-29 17:26                   ` John MacFarlane
     [not found]                     ` <m28s2slgz3.fsf-jF64zX8BO0+FqBokazbCQ6OPv3vYUT2dxr7GGTnW70NeoWH0uzbU5w@public.gmane.org>
2021-07-19 12:25                       ` AW: " denis.maier-NSENcxR/0n0
2021-06-28 23:55           ` John MacFarlane
     [not found]             ` <m2o8bplf2q.fsf-jF64zX8BO0+FqBokazbCQ6OPv3vYUT2dxr7GGTnW70NeoWH0uzbU5w@public.gmane.org>
2021-06-29  5:57               ` John MacFarlane
2021-06-29  8:54               ` AW: " denis.maier-NSENcxR/0n0
     [not found]                 ` <bae49311ad1f4a49b925be9caa80a4aa-NSENcxR/0n0@public.gmane.org>
2021-06-29  8:57                   ` denis.maier-NSENcxR/0n0

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='sb5hjc$ene$1@ciao.gmane.io' \
    --to=amphiboly-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).