Opened 18 months ago

Closed 17 months ago

Last modified 17 months ago

#5451 closed defect (fixed)

Japanese PDF build fails by not finding fonts

Reported by: strk Owned by: robe
Priority: medium Milestone: PostGIS 3.4.0
Component: l18n Version: master
Keywords: Cc:

Description

Spotted on woodie: https://woodie.osgeo.org/postgis/postgis/build/669/57

Build postgis-out.pdf
kpathsea: Running mktextfm HaranoAjiMincho/OT
/usr/share/texlive/texmf-dist/web2c/mktexnam: Could not map source abbreviation O for OT.
/usr/share/texlive/texmf-dist/web2c/mktexnam: Need to update /usr/share/texlive/texmf-dist/fonts/map/fontname/special.map?
mktextfm: Running mf-nowin -progname=mf \mode:=ljfour; mag:=1; nonstopmode; input OT
This is METAFONT, Version 2.7182818 (TeX Live 2019/Debian) (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. 

Change History (6)

comment:1 by strk, 18 months ago

I noticed that on my system, where the mktextfm HaranoAjiMincho/OT command also fails with the same error, the PDF is built successfully, so there must be something else. Woodie ends with:

mktextfm: `mf-nowin -progname=mf \mode:=ljfour; mag:=1; nonstopmode; input OT' failed to make OT.tfm.
xelatex failed
/woodpecker/src/git.osgeo.org/gitea/postgis/postgis/doc/po/ja/texstyle.sty:12: Package fontspec Error: The font "HaranoAjiMincho" cannot be found. 

comment:2 by strk, 18 months ago

Previous discussion about this was in #5439

comment:3 by strk, 18 months ago

Commenting out setCJKmainfont lines in doc/po/ja/texstyle.sty fixes the build on woodie

comment:4 by Sandro Santilli <strk@…>, 17 months ago

Resolution: fixed
Status: newclosed

In 88bb1e1/git:

Use ipafont for japanese

Closes #5451 fixing woodie builds

comment:5 by strk, 17 months ago

Debbie is happy with the change, here's the resulting japanese PDF: http://postgis.net/stuff/postgis-3.4-ja.pdf

comment:6 by strk, 17 months ago

Note that woodie will still fail until the new docker image is published, which is blocked by #5457

Note: See TracTickets for help on using tickets.