[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Font names convention
From: |
Urs Liska |
Subject: |
Font names convention |
Date: |
Thu, 18 Jan 2018 16:45:05 +0100 |
User-agent: |
Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.5.2 |
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 other fonts.
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 is also what is shown in the
properties of the PDF, but with different entries for the different font
weights.
the "name" of the Lua font object is
"AdobeGaramondPro:mode=node;script=latn;language=DFLT;+tlig;"
This looks like it could be massaged to "Adobe Garamond Pro", but I'm
really not sure this is the way to go. Is *that* approach of CamelCasing
a general rule? What about Fonts that have CamelCase in their actual
name? What about fonts that Have consecutive capitals in their name?
Is there any reliable way to get the name to be used for LilyPond out of
LuaLaTeX?
Urs
- Font names convention,
Urs Liska <=