Github messages for voidlinux
 help / color / mirror / Atom feed
From: ericonr <ericonr@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [ISSUE] [CLOSED] Texlive 2019 issues with xetex and CJK fonts
Date: Mon, 15 Feb 2021 06:51:53 +0100	[thread overview]
Message-ID: <20210215055153.poj1MR-2E3q0ugEh-iwaJRu11fUD46RSmsNCiSEJmL4@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: 2307 bytes --]

Closed issue by KRSHK on void-packages repository

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

Description:
### System

* xuname:  
  *Void 4.19.46_1 x86_64 GenuineIntel uptodate rrFF*

* package:  
  *texlive-bin-2019_1*

### Expected behavior

When compiling with ```xelatex``` a ```.tex``` file using CJKfonts from local ```.fonts``` directory, using ```xecjk``` package, it has to produce a pdf.

### Actual behavior

Since I reboot after important update, the same process give :
```
kpathsea: Running mktextfm rmplus/OT
/opt/texlive/2019/texmf-dist/web2c/mktexnam: Could not map source abbreviation  for OT.
/opt/texlive/2019/texmf-dist/web2c/mktexnam: Need to update ?
mktextfm: Running mf-nowin -progname=mf \mode:=ljfour; mag:=1; nonstopmode; input OT
This is METAFONT, Version 2.7182818 (TeX Live 2019) (preloaded base=mf)


kpathsea: Running mktexmf OT
! I can't find file `OT'.
<*> \mode:=ljfour; mag:=1; nonstopmode; input OT

Please type another input file name
! Emergency stop.
<*> \mode:=ljfour; mag:=1; nonstopmode; input OT

Transcript written on mfput.log.
grep: OT.log: Aucun fichier ou dossier de ce type
mktextfm: `mf-nowin -progname=mf \mode:=ljfour; mag:=1; nonstopmode; input OT' failed to make OT.tfm.
kpathsea: Appending font creation commands to missfont.log.


! Package fontspec Error: The font "rmplus" cannot be found.

For immediate help type H <return>.
 ...

l.25 ...infont{rmplus}[Script=CJK, Language=Japanese]
                                                  {rounded-mplus-1p-regular}

```

### Steps to reproduce the behavior
You need ```xetex``` and ```xecjk``` installed, and use the minimal example below:
```
\documentclass[9pt]{article}
\usepackage{%
     fontspec,%
     xeCJK%
 }

\setmainfont{Latin Modern Mono} %your favorite font
\setCJKmainfont{rmplus}[Script=CJK, Language=Japanese]{rounded-mplus-1p-regular}
 %your favorite CJK font, hre rounded M+ 1p regular

\begin{document}
test
{\CJKfamily{rmplus} テスト}
\end{document}
```

### More
I discovered it after trying to use upTex. I had to install new packages with ```tlmgr``` and reboot.
I tought I made some mess with mapping and everything else, so I reinstalled from scratch voidlinux. The result is the same.

  parent reply	other threads:[~2021-02-15  5:51 UTC|newest]

Thread overview: 6+ 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:35 ` svenper
2020-04-11 17:36 ` svenper
2021-02-15  5:51 ` ericonr
2021-02-15  5:51 ` ericonr [this message]
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=20210215055153.poj1MR-2E3q0ugEh-iwaJRu11fUD46RSmsNCiSEJmL4@z \
    --to=ericonr@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).