Am 18.01.2018 um 17:52 schrieb Shane Brandes:
Fonts are slightly weird
Indeed, I had that experience before (for example when trying to make
LilyPond load fonts installed as system fonts. This failed because
fontconfig *always* returns (at least it did so when I was trying)
*some* font whe
Am 18.01.2018 um 17:05 schrieb Werner LEMBERG:
When in the .tex file I write
\setmainfont{Adobe Garamond Pro}
the font is correctly used, but the "fullname" I get out of the Lua
object is "AGaramondPro-Regular".
This looks like the PostScript name.
Indeed, but it's the output of the "na
Fonts are slightly weird and are encoded with both a name, with or
without a style subset name, and a human readable name which can be
irritatingly different from the actual name. There can be no spaces in
the names which is why the difference in Human readable and the
programming name. As far as
> When in the .tex file I write
>
> \setmainfont{Adobe Garamond Pro}
>
> the font is correctly used, but the "fullname" I get out of the Lua
> object is "AGaramondPro-Regular".
This looks like the PostScript name.
> This is also what is shown in the properties of the PDF, but with
> differen
On Thu 18 Jan 2018 at 16:45:05 (+0100), Urs Liska wrote:
> Hi,
>
> I am having problems getting text font names right.
>
> From LuaLaTeX I get the information about the currently used font,
> and I inject this into a LilyPond file. This works well with "Linux
> Libertine O", but it may fail with
