public inbox archive for pandoc-discuss@googlegroups.com
 help / color / mirror / Atom feed
From: BPJ <melroch-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: pandoc-discuss <pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
Subject: Re: Is there a YAML metablock option for\defaultfontfeatures that applies to all fonts?
Date: Sun, 16 Jan 2022 19:50:45 +0100	[thread overview]
Message-ID: <CADAJKhAUzFonA0QV=CHdCNjXxdm1Sd9ojrHhPfoLAVcOiYAjHQ@mail.gmail.com> (raw)
In-Reply-To: <b61eb953-f4a4-6952-cd02-e3f9c14a871b-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>

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

You can easily add a defaultfontfeatures variable to a local template.

Den sön 16 jan. 2022 08:14R (Chandra) Chandrasekhar <chyavana-Re5JQEeQqe8@public.gmane.orgm>
skrev:

> There are occasions when I use the LaTeX command
>
>
> \defaultfontfeatures{Mapping=TeX,Scale=MatchLowercase,Ligatures=TeX,Renderer=HarfBuzz}
>
> which would apply across all the different fonts in the document.
>
> I realize that in the YAML metablock there are individual settings like
> mainfontoptions, sansfontoptions, etc.
>
> But is there a generic YAML setting that will span across _all_ fonts
> being used in a document that will supplant the \defaultfontfeatures
> declaration above?
>
> I am at present using this declaration in a .tex file that is then
> called with an --include-in-header invocation with a file argument in
> the command line.
>
> 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/b61eb953-f4a4-6952-cd02-e3f9c14a871b%40gmail.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/CADAJKhAUzFonA0QV%3DCHdCNjXxdm1Sd9ojrHhPfoLAVcOiYAjHQ%40mail.gmail.com.

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

      parent reply	other threads:[~2022-01-16 18:50 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-16  7:13 R (Chandra) Chandrasekhar
     [not found] ` <b61eb953-f4a4-6952-cd02-e3f9c14a871b-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2022-01-16 18:50   ` BPJ [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='CADAJKhAUzFonA0QV=CHdCNjXxdm1Sd9ojrHhPfoLAVcOiYAjHQ@mail.gmail.com' \
    --to=melroch-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).