public inbox archive for pandoc-discuss@googlegroups.com
 help / color / mirror / Atom feed
From: <denis.maier-NSENcxR/0n0@public.gmane.org>
To: <jgm-TVLZxgkOlNX2fBVCVOL8/A@public.gmane.org>,
	<pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>,
	<wlupton-QSt+ys/nuMyEUIsrzH9SikB+6BGkLq7r@public.gmane.org>,
	<amphiboly-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Subject: AW: AW: Citeproc is bringing a question mark inside quotes?
Date: Tue, 29 Jun 2021 08:54:36 +0000	[thread overview]
Message-ID: <bae49311ad1f4a49b925be9caa80a4aa@unibe.ch> (raw)
In-Reply-To: <m2o8bplf2q.fsf-jF64zX8BO0+FqBokazbCQ6OPv3vYUT2dxr7GGTnW70NeoWH0uzbU5w@public.gmane.org>



> -----Ursprüngliche Nachricht-----
> Von: John MacFarlane <jgm-TVLZxgkOlNX2fBVCVOL8/A@public.gmane.org>
> Gesendet: Dienstag, 29. Juni 2021 01:55
> An: Maier, Denis Christian (UB) <denis.maier-NSENcxR/0n0@public.gmane.org>; pandoc-
> discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org; wlupton-QSt+ys/nuMyEUIsrzH9SikB+6BGkLq7r@public.gmane.org;
> amphiboly-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org
> Betreff: Re: AW: Citeproc is bringing a question mark inside quotes?
> 
> 
> Here's the test that fails if we remove the global punctuation inside quotes
> transformation:
> 
>     pandoc-citeproc-move-period-inside-quote.md
>       #1:                                                            FAIL (0.08s)
>         --- test/command/pandoc-citeproc-move-period-inside-quote.md
>         +++ pandoc --citeproc -t markdown-citations
>         +   1 Here is a "test citation".[^1]
>         -   1 Here is a "test citation."[^1]
> 
> I can look into whether I can target this better so it only affects citations.
> 
> Also, citeproc brings ! and ? inside quotes; I hadn't noticed that the CSL spec
> just says to bring , and . inside. I can change that.

Oh, I have probably been confused and confusing... Clearly, regarding citations we should of course abide by the spec, and revise that if necessary. (Here, I think the problem is not so severe since we usually don't have question marks or exclamation marks that are not part of the title. Punctuation that is used to separate bibliographic elements are usally periods or commas anyway.)

But, in with quotations there are a lot of border cases. Like the behaviour prescribed by the Chicago Manual of Style: Put periods and commas inside quotation marks in all cases, but question marks and exclamation marks only if they appear in the quoted matter, i.e. in the original source. And, with German and British: Punctuation should only appear inside quotation marks when it was there in the quoted matter. Sometimes there's even a further restriction: Punctuation should only appear inside quotation marks when it was there in the quoted matter, and if we're quoting a complete sentence.

Denis


> 
> <denis.maier-NSENcxR/0n0@public.gmane.org> writes:
> 
> > Hi,
> >
> >> -----Ursprüngliche Nachricht-----
> >> Von: pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
> >> <pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org> Im Auftrag von John MacFarlane
> >> Gesendet: Montag, 28. Juni 2021 19:22
> >> An: William Lupton <wlupton-QSt+ys/nuMyEUIsrzH9SikB+6BGkLq7r@public.gmane.org>; pandoc-discuss
> >> <pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
> >> Betreff: Re: Citeproc is bringing a question mark inside quotes?
> >>
> >>
> >> In addition to what others have said, I'll note that you can change
> >> the attribute punctuation-in-quote on the style element of your style
> >> to 'false'. That will disable all punctuation moving around quotes.
> >>
> >> Another option (if you just have a few special cases where you want
> >> to defeat this behavior) might be using a zero-width unicode space.
> >>
> >> I'm sympathetic to the complaint that this movement should only
> >> affect citations, not other parts of the document.  I can't recall at
> >> the moment why I implemented it this way.
> >
> > I don't know for sure, of course, but I guess that has two reasons:
> > 1. it's been already that way with pandoc-citeproc.
> > 2. that's been done in the spirit of DRY as this behaviour is also needed for
> switching from in-text citation styles to note styles, right?
> >
> > FWIW, maybe this behaviour should be restricted to periods and commas,
> which will be moved in US English. Or it should be at least made configurable
> which punctuation marks get moved. And finally, the problem brought up by
> Rik:
> >
> >> 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.
> >
> > This brings up the older question of whether we need a more semantically
> aware punctuation moving mechanism (see
> https://github.com/jgm/citeproc/issues/6 and already
> https://github.com/jgm/pandoc-citeproc/issues/354).
> > Note: There's been a bit of a discussion on this on the org-mode list,
> > with the first implementation about here:
> > https://lists.gnu.org/archive/html/emacs-orgmode/2021-05/msg00714.html
> > There's been some back and forth since, and we've now settled (more or less)
> on this:
> >
> >>  "A quotation ending without punctuation" [cite: @hoel-71-whole].
> >  > "A quotation ending with a period"[cite: @hoel-71-whole].
> >>
> >> IOW, the presence or absence of a space before the citation
> >> determines, according to a note rule, if the punctuation should go
> >> inside or outside the quotation. (Nicolas Goaziou,
> >> https://lists.gnu.org/archive/html/emacs-orgmode/2021-06/msg00384.htm
> >> l)
> >
> > I don't know if that's the best solution, and if that would be a good fit for
> pandoc conceptually, but I wanted to at least mention it here.
> >
> > Denis
> >
> >
> >> If someone wants to put up an issue at
> >> https://github.com/jgm/citeproc/issues
> >> requesting that punctuation movement only affect processed citations,
> >> I'll look into it.
> >>
> >> --
> >> 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/m2eeclnbu5.fsf%40MacBook-Pro-2.hsd1.ca.comcast.net.

-- 
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/bae49311ad1f4a49b925be9caa80a4aa%40unibe.ch.


  parent reply	other threads:[~2021-06-29  8:54 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
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               ` denis.maier-NSENcxR/0n0 [this message]
     [not found]                 ` <bae49311ad1f4a49b925be9caa80a4aa-NSENcxR/0n0@public.gmane.org>
2021-06-29  8:57                   ` AW: " 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=bae49311ad1f4a49b925be9caa80a4aa@unibe.ch \
    --to=denis.maier-nsencxr/0n0@public.gmane.org \
    --cc=amphiboly-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org \
    --cc=jgm-TVLZxgkOlNX2fBVCVOL8/A@public.gmane.org \
    --cc=pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org \
    --cc=wlupton-QSt+ys/nuMyEUIsrzH9SikB+6BGkLq7r@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).