Github messages for voidlinux
 help / color / mirror / Atom feed
From: svenper <svenper@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: Texlive 2019 issues with xetex and CJK fonts
Date: Sat, 11 Apr 2020 19:36:21 +0200	[thread overview]
Message-ID: <20200411173621.xFV8q7JZRxTjhoyssaeTddRahEC7CWba8yHd3AUdD-I@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-11963@inbox.vuxu.org>

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

New comment by svenper on void-packages repository

https://github.com/void-linux/void-packages/issues/11963#issuecomment-612472624

Comment:
Whenever the log mentions METAFONT, it's not using OpenType or TrueType fonts normally used with XeTeX. Usually it can't find the font, but the Path option to fontspec can work around this.

If a system update is involved, have you tried regenerating formats etc?
```
sudo mktexlsr
sudo fmtutil --sys --all
sudo updmap --sys --syncwithtrees
sudo updmap --sys
```

My impressions:

```
\setCJKmainfont{rmplus}[Script=CJK, Language=Japanese]{rounded-mplus-1p-regular}
```
 looks wrong, there should be only one font name, i.e. one of
```
\setCJKmainfont[Script=CJK, Language=Japanese]{‹name›}
\setCJKmainfont{‹name›}[Script=CJK, Language=Japanese]
```

and there is no need for 
```
\CJKfamily{rmplus}
```
since script should be detected automatically by unicode range.

This works for me:™

```
\documentclass{article}
\usepackage{fontspec,xeCJK}
\setmainfont{SourceSerifPro-Regular.otf}[Path=/tmp/]
\setCJKmainfont{SourceHanSerif-Regular.otf}[Path=/tmp/,Script=CJK,Language=Japanese]
\begin{document}
test テスト
\end{document}
```

I would recommend asking on [tex.stackexchange.com](https://tex.stackexchange.com), that's where the TeX devs hang out.


  parent reply	other threads:[~2020-04-11 17:36 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-11963@inbox.vuxu.org>
2020-04-11 17:33 ` svenper
2020-04-11 17:35 ` svenper
2020-04-11 17:36 ` svenper [this message]
2021-02-15  5:51 ` ericonr
2021-02-15  5:51 ` [ISSUE] [CLOSED] " ericonr
2021-02-15  5:52 ` ericonr
2021-02-15  5:52 ` ericonr

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=20200411173621.xFV8q7JZRxTjhoyssaeTddRahEC7CWba8yHd3AUdD-I@z \
    --to=svenper@users.noreply.github.com \
    --cc=ml@inbox.vuxu.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).