public inbox archive for pandoc-discuss@googlegroups.com
 help / color / mirror / Atom feed
From: John MacFarlane <jgm-TVLZxgkOlNX2fBVCVOL8/A@public.gmane.org>
To: "R (Chandra) Chandrasekhar"
	<chyavana-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>,
	pandoc-discuss
	<pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
Subject: Re: Smart quotes with roman, sans serif and mono fonts and LaTeX
Date: Sun, 12 Sep 2021 11:00:56 -0700	[thread overview]
Message-ID: <m2ilz5znaf.fsf@MacBook-Pro-2.hsd1.ca.comcast.net> (raw)
In-Reply-To: <74247170-9cd6-6e28-8443-b6d93c1f824f-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>


In a raw LaTeX context, smart quote recognition won't work.
Use unicode curly quotes inside \textsf{...}.



"R (Chandra) Chandrasekhar" <chyavana-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> writes:

> I want to get smart quotes with a sans serif font with LaTeX/PDF output 
> from markdown input.
>
> The quotes I got with \textsf{"This is it."} were not paired, but two of 
> the same.
>
> My MWE, in a file named quotes.md, is:
>
> ---
> mainfont: "Noto Serif"
> sansfont: "Noto Sans"
> monofont: "Noto Mono"
> ---
>
> "This is it."
>
> \textrm{"This is it."}
>
> \textsf{"This is it."}
>
> \texttt{"This is it."}
>
> `"This is it."`
>
> ---End of MWE---
>
> When compiled with
>
> pandoc -f markdown -t latex --pdf-engine lualatex --output quotes.pdf 
> quotes.md
>
> I get properly paired quotes when used outside of \textrm declaration, 
> but not within it.
>
> Of course, the monofont does not have two types of quotes and so appears 
> the same in both invocations.
>
> My question is how do I get correctly paired sans serif quotes to show 
> up in the PDF?
>
> I do not want to do
>
> \renewcommand{\familydefault}{\sfdefault}
>
> since I wish to have the sans serif font only in selected parts of the 
> output.
>
> Thanks.
>
> Chandra
>
> -- 
> 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/74247170-9cd6-6e28-8443-b6d93c1f824f%40gmail.com.


      parent reply	other threads:[~2021-09-12 18:00 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-09-12 17:36 R (Chandra) Chandrasekhar
     [not found] ` <74247170-9cd6-6e28-8443-b6d93c1f824f-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2021-09-12 18:00   ` John MacFarlane [this message]

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=m2ilz5znaf.fsf@MacBook-Pro-2.hsd1.ca.comcast.net \
    --to=jgm-tvlzxgkolnx2fbvcvol8/a@public.gmane.org \
    --cc=chyavana-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).