···<date: 2013-11-19, Tuesday>···<from: Petr Olsak>···
> >> I am sure that the same version of luaotfload files are used (from tl2013
> >> tree). The \fontname returns bad string:
> >
> > You may have to update Luaotfload, this issue was fixed months ago.
> > You can check which version is installed by running
> >
> > luaotfload-tool -V
> >
> > The latest version on CTAN is v2.3b.
>
> Thanks. After tlmgr update --all I have installed the 2.3b version on
> my computer and the \fontname returns fontfeatures.
>
> But there is new problem with \fontname: When user writes the \font
> parameter in the "quotes" (because fontname can include a space), then
> these quotes are lost in \fontname output but in XeTeX they are kept.
> Example:
>
> \ifx\luatexversion\undefined \else \input luaotfload.sty \fi
> \font\hello="Luxi Mono Regular" at 12pt
> \message{::: \fontname\hello}
> \end
>
> $ xetex test
> ...
> ::: "Luxi Mono Regular" at 12.0pt
>
>
> $ luatex test
> ...
> ::: Luxi Mono Regular at 12.0pt
That shouldn’t happen. Luaotfload auto-quotes the specification
when passing it into a font’s name field.
https://github.com/lualatex/luaotfload/commit/9cdf846537280dc9661b1ed88a58eb763b237d1d
Could it be you have some old files left that cause interference?
Best,
Philipp
pgpHs_k0H3PoK.pgp
Description: PGP signature
