Bug#683943: luatex: fontconfig overridden by OSFONTDIR in default settings
On 12 August 2012 11:31, Frank Kuester <frank@kuesterei.ch> wrote:
>
> Anyway, what I am not sure about is what we should do about this. The
> documentation in texmf.cnf says:
>
> % OSFONTDIR is to provide a convenient hook for allowing TeX to find
> % fonts installed on the system (outside of TeX). An empty default
> % value would add "//" to the search paths, so we give it a dummy value.
> OSFONTDIR = /usr/share/fonts
>
> I am not sure whether luatex is correct in taking this as an alternative
> to fontconfig.
As far as I can tell, that is what OSFONTDIR is for. The
mkluatexfontdb script, which presumably is trying to mimic the
behaviour of luatex, also has this behaviour.
> The other question is which other engines use OSFONTDIR. Note that some
> other variables reference it, and need the "dummy setting" for speed:
>
> T1FONTS = .;$TEXMF/fonts/type1//;$OSFONTDIR//
> AFMFONTS = .;$TEXMF/fonts/afm//;$OSFONTDIR//
> TTFONTS = .;$TEXMF/fonts/{truetype,opentype}//;$OSFONTDIR//
> OPENTYPEFONTS = .;$TEXMF/fonts/{opentype,truetype}//;$OSFONTDIR//
>
> So it could be that we would need to have a OSFONTDIR.luatex variable
> instead that is empty?
I don't think that would work, because an empty variable would make it
search no paths (not the same as unsetting the variable, which as far
as I can tell is impossible in kpathsea).
If that is correct, then OSFONTDIR should not be set, but per-engine
versions should be set for whichever engines need it. As far as I can
tell, the only engines not using fontconfig are tex and ptex.
--
http://rrt.sc3d.org
Reply to: