public inbox archive for pandoc-discuss@googlegroups.com
 help / color / mirror / Atom feed
From: <denis.maier-NSENcxR/0n0@public.gmane.org>
To: <pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
Cc: <Pierre-Louis.Blanchard-U0LLASLCtz9qrsqc6uq6we1GAupnlqi7@public.gmane.org>
Subject: csquotes configuration options / loading of header-includes
Date: Wed, 21 Jun 2023 07:09:34 +0000	[thread overview]
Message-ID: <813195abd91948e5a13c44c3babe5891@unibe.ch> (raw)

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

Hi,

I've tried to modify the behaviour of csquotes. In particular, I wanted to use guillemets when writing in German. I've realized a couple of things:

- There is currently no easy way to modify the package behaviour. No csquotes-options metadata variable or something similar. Any reason not to add this ?
- With csquotes you can set package options also via  `\ExecuteQuoteOptions{}`, so I tried `\ExecuteQuoteOptions{german=guillemets}`. However, pdflatex now complained about `\ExecuteQuoteOptions{}` being undefined. Apparently, `header-includes` stuff is added to the preamble before the csquotes package is loaded. Is there any reason for this? Wouldn't it make more sense to defer the loading of header-includes material until later in the template?
- Using `header-includes: \usepackage[german=guillemets]{csquotes}` doesn't work either, because that way pandoc will not realize that the csquotes packages is actually used.
- This here will work though:


```
header-includes: \usepackage[german=guillemets]{csquotes}
csquotes: true
```
This will cause pandoc to use \enquote, and loading csquotes twice doesn't seem to do any harm. Yet, I'd argue that this is poor style.

So, to sum up, anything speaking against adding a new option csquotes-options *and* moving \usepackage{csquotes} up in the template / header-includes down? (As per common knowledge, hyperref should probably come last, but I don't see why natbib or biblatex should be loaded after header-includes.)

Best,
Denis

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

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

                 reply	other threads:[~2023-06-21  7:09 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=813195abd91948e5a13c44c3babe5891@unibe.ch \
    --to=denis.maier-nsencxr/0n0@public.gmane.org \
    --cc=Pierre-Louis.Blanchard-U0LLASLCtz9qrsqc6uq6we1GAupnlqi7@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).