problem with xetex access to system fonts
Sorry, I don't know whether is it wrong list!
I have installed texlive texlive-latex-recommended, texlive-fonts-recommended,
texlive-latex-base, texlive-base, texlive-latex-extra texlive-xetex
,lmodern packages
on squeeze using aptitude.
I read some TUG's documents about testing the texlive installtion on
http://tug.org/texlive/doc/texlive-en/texlive-en.html#x1-390003.5,
"After installing TEX Live as best you can, you naturally want to test it out,
so you can start creating beautiful documents and/or fonts."
(...)
If you have installed the xetex package, you can test its access to
system fonts as follows:
> xetex opentype-info.tex
This is XeTeX, Version 3.1415926…
...
Output written on opentype-info.pdf (1 page).
Transcript written on opentype-info.log.
If you get an error message saying “Invalid fontname ‘Latin Modern Roman/ICU’…”,
then you need to configure your system so that XeTEX can find the fonts shipped
with TEX Live. See Section 3.4.4.
(...)
and I try it myself. All test passed except xetex. I am confused with
that though I can
use xelatex access some system fonts (eg: AR PL UMing CN, Liberation serif).
See below:
$: xetex opentype-info.tex
This is XeTeX, Version 3.1415926-2.2-0.9995.2 (TeX Live 2009/Debian)
entering extended mode
(./opentype-info.texkpathsea: Invalid fontname `Latin Modern
Roman/ICU', contains ' '
! Font \testfont="Latin Modern Roman/ICU" at 12.0pt not loadable: Metric (TFM)
file or installed font not found.
l.26 \font\testfont="\myfontname/ICU" at 12pt
?
According to http://tug.org/texlive/doc/texlive-en/texlive-en.html#x1-350003.4.4,
it seems that I need copy TEXMFSYSVAR/fonts/conf/texlive-fontconfig.conf file to
/etc/fonts/conf.d/09-texlive.conf. But I can't find
texlive-fontconfig.conf in /var/lib/texmf/fonts.
I have asked on debian-users@lists.debian.org and then add some lines
to ~/.fonts.conf,
<?xml version='1.0'?>
<!DOCTYPE fontconfig SYSTEM 'fonts.dtd'>
<fontconfig>
<dir>/usr/share/texmf/fonts/opentype</dir>
<dir>/usr/share/texmf/fonts/type1</dir>
</fontconfig>
and try again, it works well. But I am not sure whether it's the
right way and why aptitude
not do this job for me. Is it a bug?
Sorry for my poor English!
Greetings,
Zhang Qide
Reply to: