Re: Font names convention

[Shane Brandes]

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 camel case it will make a font that is
entirely different in being requested to one in all caps or all lower
case of the same letters. Anyway, it really can prove a headache in
some cases. The most accurate method I can recommend for examining
this stuff is using Fontforge which is probably a bit much power just
to check on such things.

regards,

Shane

On Thu, Jan 18, 2018 at 11:05 AM, Werner LEMBERG <address@hidden> wrote:
>
>> 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
>> 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.
>
> [I'm not a luatex user.]  This appears to be name ID 1 taken from the
> font's `name' table, with spaces removed.  I strongly suggest that you
> get confirmation on a luatex list or forum.
>
> Look also at the output of `fc-list -v', entries `family'
> vs. `fullname'.
>
>> 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?
>
> There is certainly no magic here.  Those camel casing is already
> present in the font (or it happens as soon as spaces get removed).
>
>> Is there any reliable way to get the name to be used for LilyPond
>> out of LuaLaTeX?
>
> I'm very confident that this is possible, since luatex parses the font
> tables by itself.  Again a question for a luatex list...
>
>
>     Werner
> _______________________________________________
> lilypond-user mailing list
> address@hidden
> https://lists.gnu.org/mailman/listinfo/lilypond-user