From: Lyndon Drake <isenguard-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: pandoc-discuss <pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
Subject: Re: LaTeX template and options for other languages
Date: Sat, 23 Apr 2022 22:54:12 -0700 (PDT) [thread overview]
Message-ID: <c873e83b-6b98-45c7-971c-9ce76db4e761n@googlegroups.com> (raw)
In-Reply-To: <20220424.064450.715388246013095648.wl-mXXj517/zsQ@public.gmane.org>
[-- Attachment #1.1: Type: text/plain, Size: 1657 bytes --]
Good point, I was looking at an out-of-date babel documentation PDF. I've
altered it to:
\babelprovide[import,onchar=ids fonts]{hebrew}
\babelfont[*hebrew]{rm}[Renderer = Harfbuzz, ItalicFont =
TaameyDavidCLM-MediumOblique, BoldFont = TaameyDavidCLM-Bold,
BoldItalicFont = TaameyDavidCLM-BoldOblique]{TaameyDavidCLM-Medium}
which I think is the correct approach (font change not needed if the main
font already provides the appropriate script).
My main question still stands though regarding the \babelprovide. I don't
know if we could potentially change the default LaTeX template to have this:
\babelprovide[import,onchar=ids fonts]{$babel-otherlangs$}
to get the automatic font/script switching that the bidi algorithm provides?
And is there a way to tell pandoc that there are additional languages, in a
way that feeds into the babel-otherlangs variable and triggers that section
of the default template?
Lyndon
On Sunday, 24 April 2022 at 16:45:00 UTC+12 Werner wrote:
> > ```
> > \babelprovide[import,onchar=ids,mapfont=direction]{hebrew}
> > ...
> > ```
>
> Are you sure about this? The documentation of Babel v3.73 says the
> following for option `onchar`:
>
> This option is not compatible with `mapfont`.
>
>
> Werner
>
--
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/c873e83b-6b98-45c7-971c-9ce76db4e761n%40googlegroups.com.
[-- Attachment #1.2: Type: text/html, Size: 2437 bytes --]
prev parent reply other threads:[~2022-04-24 5:54 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-24 1:28 Lyndon Drake
[not found] ` <9d3c0e5b-ba6c-4268-bbc8-4ee57d0e0722n-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2022-04-24 4:44 ` Werner LEMBERG
[not found] ` <20220424.064450.715388246013095648.wl-mXXj517/zsQ@public.gmane.org>
2022-04-24 5:54 ` Lyndon Drake [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=c873e83b-6b98-45c7-971c-9ce76db4e761n@googlegroups.com \
--to=isenguard-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).