From: Sukil Etxenike arizaleta <sukiletxe-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
Subject: Re: Changing typographical quotation marks in citations
Date: Thu, 30 Jun 2022 14:34:06 +0200 [thread overview]
Message-ID: <e4a10b1a-a31b-109f-58b7-8b6213593f22@gmail.com> (raw)
In-Reply-To: <da178cb2-48fa-4f53-8417-02dcae0129acn-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
[-- Attachment #1: Type: text/plain, Size: 2405 bytes --]
Hi,
After looking at the spec (the only experience I have with CSL files), I
think you would need to modify your CSL file, Add a locale element in
the root style element, like this:
<style>
<locale xml:lang="en">
<terms>
<term name = "open-quote">«</term>
<term name = "close-quote">»</term>
</terms>
</locale>
</style>
(Or try left-inner-quote and right-inner quote instead, maybe)
Hth,
Sukil
El 30/06/2022 a las 14:04, John Carter Wood escribió:
> In setting up a CSL file for a German-language publisher (but for
> English-language texts), I've run into the issue of needing to change
> the typographical quotation marks when converting from Markdown to
> docx or pdf. I am familiar with pandoc-quotes.lua but when using it,
> it changes the quote marks in the main text, but not in the citations
> (which come from a json file).
>
> So, I have to use this group of quotation marks: »«›‹, which I have
> set in a YAML block (quot-marks: »«›‹). (The document language is set
> to en-GB.)
>
> The result changes the main text quotation marks but not the citations
> (see screenshot).
>
> Screenshot from 2022-06-30 13-55-41.png
>
> Is there a way of getting the quotation marks I want in the citations
> as well?
>
> (pandoc-version 2.18)
> --
> 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/da178cb2-48fa-4f53-8417-02dcae0129acn%40googlegroups.com
> <https://groups.google.com/d/msgid/pandoc-discuss/da178cb2-48fa-4f53-8417-02dcae0129acn%40googlegroups.com?utm_medium=email&utm_source=footer>.
--
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/e4a10b1a-a31b-109f-58b7-8b6213593f22%40gmail.com.
[-- Attachment #2: Type: text/html, Size: 4281 bytes --]
next prev parent reply other threads:[~2022-06-30 12:34 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-30 12:04 John Carter Wood
[not found] ` <da178cb2-48fa-4f53-8417-02dcae0129acn-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2022-06-30 12:34 ` Sukil Etxenike arizaleta [this message]
[not found] ` <e4a10b1a-a31b-109f-58b7-8b6213593f22-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2022-06-30 12:41 ` John Carter Wood
[not found] ` <062deeeb-9dfb-4ca3-ae3a-10b360293315n-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2022-06-30 16:23 ` BPJ
[not found] ` <CADAJKhAaLedtM4gWri6L-OFxG0aPoLA24w71Wn8zw+M-QxQe4g-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2022-06-30 16:29 ` John Carter Wood
[not found] ` <0db7e968-6c00-4399-bd8e-a7b2ad46a841n-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2022-06-30 17:53 ` BPJ
[not found] ` <CADAJKhATktFtxGyijTU7z8S34sOG0RmfQwRatSuQVB2ODSgyKg-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2022-06-30 20:25 ` John Carter Wood
[not found] ` <8c8c4dcc-5189-4b88-833d-c9154d1d2fb1n-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2022-07-01 14:15 ` 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=e4a10b1a-a31b-109f-58b7-8b6213593f22@gmail.com \
--to=sukiletxe-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).