public inbox archive for pandoc-discuss@googlegroups.com
 help / color / mirror / Atom feed
From: John MacFarlane <fiddlosopher-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
Subject: Re: Problem with pdf conversion, citations with titles that include terminal punctuation
Date: Fri, 6 Aug 2021 15:10:33 -0700	[thread overview]
Message-ID: <D1B3BD6E-084E-429E-B194-3CEC29689FEB@gmail.com> (raw)
In-Reply-To: <56620658-d10e-4ee7-b658-46dbc65a9ca1n-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>

[-- Attachment #1: Type: text/plain, Size: 3623 bytes --]

This looks like a bug that was fixed a couple versions ago. Try upgrading to the latest release of Pandoc.

> On Aug 6, 2021, at 7:13 AM, johanne...-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org <johannes.c.holz@gmail.com> wrote:
> 
> Thanks to a tip from a LaTeX-knowlegeable friend, I tried using the +smart extension with my pandoc command: pandoc --from markdown+smart KIII_4.md -o KIII_4-new-test.pdf --citeproc 
> 
> This solved the problem. Which is curious, since the LaTeX output looks the same in both cases. (If I export a .tex file instead of a pdf.) 
> 
> But it works! And that's the most important thing. Just wanted to leave the note here, that my question is solved. 
> 
>> On Friday, August 6, 2021 at 2:08:12 PM UTC+2 johanne...-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org wrote:
>> A quick follow-up: the problem also occurs with other terminal punctuation in titles (question marks, etc). So it's not just about the exclamation point. 
>> 
>> 
>> On Thursday, August 5, 2021 at 3:31:48 PM UTC+2 johanne...-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org wrote:
>>> Hi everyone,
>>> 
>>> I am running into a problem with the formatting of titles in footnotes and bibliographies that have concluding punctuation *in the titles* when using pandoc to convert from markdown to pdf via LaTeX.
>>> 
>>> I have a bibliographic entry in a json file that is a newspaper article with a title that ends in an exclamation point. When creating a pdf, the exclamation mark is turned upside down and the concluding quotation mark is turned into a single quotation mark. 
>>> 
>>> 
>>> 
>>> When converting to docx it converts fine.
>>> 
>>> 
>>> 
>>> It also looks fine when I preview citations in Zotero.
>>> 
>>> I am using Zotero to create a json file to contain the citations. 
>>> I am then using pandoc (2.11.3.1) and citeproc (0.3.0.1) to create the documents.
>>> Citation file and csl are defined in YAML in the markdown documents, where I also use package \csquotes. 
>>> 
>>> The json entry looks like this: 
>>> 
>>> ~~~
>>> {"id":"noauthor_stamp_1932","container-title":"Daily Mirror","event-place":"London","issued":{"date-parts":[[1932,4,30]]},"language":"en","page":"9","publisher-place":"London","title":"Stamp out these bandits!","title-short":"Stamp out these bandits!","type":"article-newspaper"},
>>> ~~~
>>> 
>>> A few notes:
>>> - The error occurs whether or not I use the pandoc-quotes.lua to get my German quotation marks. 
>>> - The error occurs with different csl files
>>> - The error occurs whether I use the default LaTeX engine or use XeTeX.
>>> - The error also occurs when exporting a .bib file from Zotero (whether in BibTeX or BibLaTeX)
>>> 
>>> I would very much appreciate any assistance in solving this problem!
>>> 
> 
> -- 
> 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/56620658-d10e-4ee7-b658-46dbc65a9ca1n%40googlegroups.com.

-- 
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/D1B3BD6E-084E-429E-B194-3CEC29689FEB%40gmail.com.

[-- Attachment #2: Type: text/html, Size: 5678 bytes --]

  parent reply	other threads:[~2021-08-06 22:10 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-08-05 13:31 John Carter Wood
     [not found] ` <292ee9a1-4fa1-f6e5-99a6-584a690a54ff-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2021-08-06 12:08   ` johanne...-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org
     [not found]     ` <4a594f48-0c39-4c71-9920-2fdc9ad05ac3n-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2021-08-06 14:13       ` johanne...-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org
     [not found]         ` <56620658-d10e-4ee7-b658-46dbc65a9ca1n-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2021-08-06 22:10           ` John MacFarlane [this message]
     [not found]             ` <D1B3BD6E-084E-429E-B194-3CEC29689FEB-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2021-08-08  9:01               ` John Carter Wood

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=D1B3BD6E-084E-429E-B194-3CEC29689FEB@gmail.com \
    --to=fiddlosopher-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).