From: "'Frederik Elwert' via pandoc-discuss" <pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
To: pandoc-discuss <pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
Subject: LaTeX: Individual words in Chinese script
Date: Fri, 10 Mar 2023 02:35:40 -0800 (PST) [thread overview]
Message-ID: <cadd3e14-3167-447f-9f64-8158a6613cb6n@googlegroups.com> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 2127 bytes --]
Hi!
We are typesetting a lot of academic texts which are mainly in English, but
contain words in other languages/scripts. At the moment, I need to produce
an article that contains individual words in traditional Chinese.
With pandoc, I currently face two issues:
First, chinese is not defined in Writers/LaTeX/Lang.hs. This means that, in
contrast to other scripts, I cannot use `[言]{lang="zh-Hant"}`. For other
languages that are defined, the LaTeX writer produces
`\foreignlanguage{}{}` commands, but in this case it produces only `{言}`.
Thus, the only possibility is to resort to `CJKmainfont`. The issue is that
this switches on xeCJK for the whole document, which has undesirable side
effects (mainly concerning spacing around punctuation characters). Thus, I
have to introduce manual `\makexeCJKactive`/`\makexeCJKinactive` commands
in my markdown source. For short passages of Chinese, it is actually
desirable not to use xeCJK, but simply babel, as with other scripts.
Second, I do not see a way to define fonts for other scripts. The default
LaTeX template calls `\babelprovide` for used fonts, but does not allow to
define corresponding `\babelfont`s. With the old polyglossia system, IIRC,
it was possible to use the `fontfamilies` metadata entry to define
`\chinesefont` etc. for additional scripts. But this does no longer work
with babel (if I’m not missing something).
So basically my question is twofold: First, how do I define additional
fonts for foreign scripts with the new babel system, and second, would it
be possible to support chinese script in the LaTeX writer in the same way
it supports other scripts?
Thanks,
Frederik
--
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/cadd3e14-3167-447f-9f64-8158a6613cb6n%40googlegroups.com.
[-- Attachment #1.2: Type: text/html, Size: 2538 bytes --]
next reply other threads:[~2023-03-10 10:35 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-10 10:35 'Frederik Elwert' via pandoc-discuss [this message]
[not found] ` <cadd3e14-3167-447f-9f64-8158a6613cb6n-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2023-03-10 18:17 ` John MacFarlane
[not found] ` <667077D3-D8A5-4B6A-9253-F3F569439ADA-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2023-03-10 20:32 ` 'Frederik Elwert' via pandoc-discuss
[not found] ` <a66a708e-6599-4cab-88a5-a89f592e8b8en-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2023-03-10 22:20 ` John MacFarlane
[not found] ` <2163FD26-E90E-472A-A94E-D20247FC7A9C-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2023-03-10 22:34 ` 'Frederik Elwert' via pandoc-discuss
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=cadd3e14-3167-447f-9f64-8158a6613cb6n@googlegroups.com \
--to=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).