From: "Pablo Rodríguez" <oinos-S0/GAf8tV78@public.gmane.org>
To: pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
Subject: Re: Single and double quotes in Context with British English
Date: Wed, 2 Aug 2023 22:26:44 +0200 [thread overview]
Message-ID: <8e63fe5e-de8b-1bdb-27d7-60fab49f2b7b@web.de> (raw)
In-Reply-To: <1513fe42-80ad-4acd-bb53-85a04ed52a7cn-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
On 8/2/23 20:54, Thomas Hodgson wrote:
> Correct me if I'm wrong, but here is how I think it works now:
>
> 'foo' -> Quoted SingleQuote [ Str "foo" ] -> \quote{foo}
> "bar" -> Quoted DoubleQuote [ Str "bar" ] -> \quotation{bar}
>
> My suggestion is that if the language is British (and maybe for some
> other varieties, I haven't checked) the result should be:
>
> 'foo' -> Quoted SingleQuote [ Str "foo" ] -> \quotation{foo}
> "bar" -> Quoted DoubleQuote [ Str "bar" ] -> \quote{bar}
>
> That would avoid my problem.
After having using ConTeXt for more than a decade (mainly without
pandoc), I think this is an issue with ConTeXt, not with pandoc.
Quotes or quotation marks aren’t set in stone. I mean, for Spanish and
any language with diacritical marks I would never use these “quotes”,
but these «ones» (either single or double). They don’t interfere with
the marks (such as “ñandú” and «ñandú»).
I’m not a native speaker and I’m mainly exposed to US English. If
British English uses double quotes for \quotation and single quotes for
\quote, you could do the following:
Either you suggest to change the default in ConTeXt itself, or you place
a file that includes the following in your local tree:
\setuplanguage[en-gb][
leftquotation=“,
rightquotation=”,
leftquote=‘,
rightquote=’,
]
I don’t have myself TeX Live installed (I use a pure ConTeXt
distribution) and in my case the file is
"$HOME/texmf/texmf-local/cont-loc.mkxl".
If you are on Windows, it would read
"%USERPROFILE%/texmf/texmf-local/cont-loc.mkxl".
After creating the file and saving the contents, it might be wise to
clean the cache and generate it again.
"mtxrun --scripts cache --erase && mtxrun --generate" does this in part.
After that, the next compilation would take longer, since it will have
to create the format file (required by ConTeXt).
Just in case it helps,
Pablo
--
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/8e63fe5e-de8b-1bdb-27d7-60fab49f2b7b%40web.de.
next prev parent reply other threads:[~2023-08-02 20:26 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-02 14:10 Thomas Hodgson
[not found] ` <6bf5b865-b98a-4eab-ac15-9ca58d38e6cfn-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2023-08-02 14:55 ` Bastien DUMONT
2023-08-02 16:27 ` Thomas Hodgson
[not found] ` <a416671d-1c67-4f4b-97c4-24b18e440466n-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2023-08-02 17:57 ` Thomas Hodgson
[not found] ` <a1f39c5a-624a-48d7-af9a-d4b7dd66f3bbn-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2023-08-02 18:19 ` Bastien DUMONT
2023-08-02 18:54 ` Thomas Hodgson
[not found] ` <1513fe42-80ad-4acd-bb53-85a04ed52a7cn-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2023-08-02 19:23 ` Bastien DUMONT
2023-08-02 20:26 ` Pablo Rodríguez [this message]
[not found] ` <8e63fe5e-de8b-1bdb-27d7-60fab49f2b7b-S0/GAf8tV78@public.gmane.org>
2023-08-03 9:46 ` Thomas Hodgson
[not found] ` <d9bcf5be-c7f3-4225-ab9e-0d4cdc8de1e6n-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2023-08-03 10:16 ` Bastien DUMONT
2023-08-03 14:23 ` Thomas Hodgson
2023-08-02 19:33 ` BPJ
2023-08-02 17:50 ` Pablo Rodríguez
[not found] ` <fc349c18-6989-67be-6a64-e701b4a06d16-S0/GAf8tV78@public.gmane.org>
2023-08-02 18:54 ` Thomas Hodgson
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=8e63fe5e-de8b-1bdb-27d7-60fab49f2b7b@web.de \
--to=oinos-s0/gaf8tv78@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).