lilypond-user
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: OTF text font family with optical sizes : unable to access regular f


From: Daniel Tobias Johansen Langhoff
Subject: Re: OTF text font family with optical sizes : unable to access regular font
Date: Tue, 27 Oct 2020 20:15:21 +0100

Sorry, no change.

A workaround is to make a copy of the regular size font files and
rename the family of those files to something else (e.g. from
"Arno Pro" to "Arno Pro Regular") using a font renaming script, like
https://github.com/chrissimpkins/fontname.py

– Daniel Tobias

On Tue, Oct 27, 2020 at 7:57 PM Aaron Hill <lilypond@hillvisions.com> wrote:
>
> On 2020-10-27 8:50 am, Daniel Tobias Johansen Langhoff wrote:
> > Hi
> >
> > I’m having an issue using the Arno Pro typeface as a text font in
> > LilyPond. When trying to use the regular font of the regular optical
> > size, "Arno Pro Caption" is being substituted, as confirmed by
> > pdffonts. Italic works as expected (as well as bold), and I can
> > explicitly specify any other font of the family, like "Arno Pro Smbd
> > Display". This bug is not happening with Garamond Premier Pro.
> >
> > I’m running LilyPond 2.20.0 on Ubuntu 20.04. I’ll happily provide more
> > information on request. First time posting to any mailing list, so I
> > hope I’m doing this correctly.
> >
> > $ cat minimal.ly
> > \paper {
> >   #(define fonts
> >     (set-global-fonts
> >      #:roman "Arno Pro"
> >     ))
> > }
> >
> > \markup {
> >   "Regular" \italic "Italic"
> > }
> > $ pdffonts minimal.ly
> > name                                 type              encoding
> >  emb sub uni object ID
> > ------------------------------------ -----------------
> > ---------------- --- --- --- ---------
> > LMLSAN+ArnoPro-Caption               Type 1C           Custom
> >  yes yes yes      8  0
> > DARGUI+ArnoPro-Italic                Type 1C           WinAnsi
> >  yes yes no      11  0
>
> Pango/font-config can do unexpected things when looking up fonts in
> larger families, especially those with non-standard naming conventions.
>
> As I do not have access to that proprietary font family for local
> testing, I cannot be certain this will work.  But try using "Arno Pro,"
> or "Arno Pro Regular," as the font name.  Note the intentional trailing
> commas there.
>
>
> -- Aaron Hill



reply via email to

[Prev in Thread] Current Thread [Next in Thread]