Re: fonts not working as expected [SOLVED, at least for OP]

[Werner LEMBERG]

> I don't regard this as done and dusted yet.

Thanks!

> It fails on a Mac pristine install for High Sierra. This is not good
> at all. I'm am continuing to look further into this very pinpoint
> specific failure pattern. It's odd.

What about trying the MacPorts version?  The package is called
`lilypond-devel' and provides 2.19.80.  This should deliver the newest
versions of all libraries.


Werner

___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: fonts not working as expected [SOLVED, at least for OP]

[Aaron Hill]

On 2018-10-31 1:59 am, Andrew Bernard wrote:

Hi All,

It's something much more subtle than the system/user font location. On 
my
system, despite Kieran's success, it does not work, and when K upgrades 
the
mac it may not work for him. In correspondence with the typographer of 
the

font, we have all definitively established what the correct version is.

This matter is specific to Alegreya, to the Mac, and to lilypond using 
it,
not other programs. It does not arise with any other font that I know 
(but
it is hard to test hundreds of thousands...) and does not arise on 
Windows

or various Linux distros.

I don't regard this as done and dusted yet. It fails on a Mac pristine
install for High Sierra. This is not good at all. I'm am continuing to 
look

further into this very pinpoint specific failure pattern. It's odd.


Hi Andrew,

I don't have access to any Mac environments, or else I'd help you chase 
this down.  But I did have a few ideas for next steps, assuming you have 
not already done them.


The GitHub for the foundry has older versions of the font family as well 
as other fonts they publish.  In the event there is something in their 
workflow that generates fonts with a rare but buggy characteristic, it 
would be good to test as many fonts there as reasonable.  Especially it 
would be good to test older versions of the fonts that known to fail.  
If the failing case is exclusive to one or more specific versions, that 
might help to track down the underlying issue.


-- Aaron Hill

___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: fonts not working as expected [SOLVED, at least for OP]

[Andrew Bernard]

Hi All,

It's something much more subtle than the system/user font location. On my
system, despite Kieran's success, it does not work, and when K upgrades the
mac it may not work for him. In correspondence with the typographer of the
font, we have all definitively established what the correct version is.

This matter is specific to Alegreya, to the Mac, and to lilypond using it,
not other programs. It does not arise with any other font that I know (but
it is hard to test hundreds of thousands...) and does not arise on Windows
or various Linux distros.

I don't regard this as done and dusted yet. It fails on a Mac pristine
install for High Sierra. This is not good at all. I'm am continuing to look
further into this very pinpoint specific failure pattern. It's odd.

Andrew



On Wed, 31 Oct 2018 at 11:57, Kieren MacMillan <
kieren_macmil...@sympatico.ca> wrote:

> Hi,
>
> > If the problem is Mac related, then it might have to do with System
> fonts (located in /Library/Fonts) vs. User fonts (located in
> Users//Library/Fonts).  IIRC, the default installation location
> when using Font Book is the User location.
>
> Good thought… but in my case, I know for sure that all fonts were
> installed at the Computer/System level. It was definitely the source (and
> therefore, likely, the version) of the font that determined success or
> failure.
>
> Cheers,
> Kieren.
> 
>
> Kieren MacMillan, composer
> ‣ website: www.kierenmacmillan.info
> ‣ email: i...@kierenmacmillan.info
>
>
> ___
> lilypond-user mailing list
> lilypond-user@gnu.org
> https://lists.gnu.org/mailman/listinfo/lilypond-user
>
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: fonts not working as expected [SOLVED, at least for OP]

[Kieren MacMillan]

Hi,

> If the problem is Mac related, then it might have to do with System fonts 
> (located in /Library/Fonts) vs. User fonts (located in 
> Users//Library/Fonts).  IIRC, the default installation location 
> when using Font Book is the User location.

Good thought… but in my case, I know for sure that all fonts were installed at 
the Computer/System level. It was definitely the source (and therefore, likely, 
the version) of the font that determined success or failure.

Cheers,
Kieren.


Kieren MacMillan, composer
‣ website: www.kierenmacmillan.info
‣ email: i...@kierenmacmillan.info


___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: fonts not working as expected [SOLVED, at least for OP]

[Br. Samuel Springuel]

If the problem is Mac related, then it might have to do with System 
fonts (located in /Library/Fonts) vs. User fonts (located in 
Users//Library/Fonts).  IIRC, the default installation 
location when using Font Book is the User location.  I've had problems 
with some programs (can't remember if Lilypond is one of them) accessing 
fonts installed for a single User (even the current one).  As a result, 
I've set things up so that all fonts are installed at the System level 
(you can change this in Font Book's preferences).  You might try 
checking where the font was installed and if it was installed at the 
User level, change it to an installation at the System level (you can 
simply move the file with Finder or Terminal) and try again.

--
✝✝
Br. Samuel, OSB
(R. Padraic Springuel)
St. Anselm’s Abbey
4501 South Dakota Ave, NE
Washington, DC, 20017
202-269-2300
(c) 202-853-7036

PAX ☧ ΧΡΙΣΤΟΣ

___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: fonts not working as expected [SOLVED, at least for OP]

[Andrew Bernard]

Hi Karlin,

I am continuing to look into it.

Andrew



> I got the latest Alegreya font version 2.008 from GitHub, added only the
> OTF font files using FontBook, and restarted the computer. So far, my Mac’s
> LilyPond has not picked up on the Alegreya font. No consequence for me, I
> don’t do production work on this machine. Moving on, unless someone wants
> some additional specific testing done.
>
>
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: fonts not working as expected

[Andrew Bernard]

Hi All,

Indeed, I just heard back from Juan Pablo del Peral re which source is
authoritative:

The latest version is on GitHub.
https://github.com/huertatipografica/Alegreya/releases/tag/v2.008

This is the official repo of the project :=)


A very fine font in my opinion. Worth solving this issue therefore.

Andrew



On Wed, 31 Oct 2018 at 03:06, Alexander Kobel  wrote:

> On 30/10/2018 14.08, Andrew Bernard wrote:
> > I have written to huertatipografica to ask where the definitive and most
> > current state of Alegreya is to be found, from their website or from
> > github. It's not clear what the relationship is between the two.
>
> Hehe, indeed that's a funny coincidence.
> Juan Pablo del Peral (the designer) answered just a couple of hours ago
> on https://github.com/huertatipografica/Alegreya/issues/17:
>
> "I just tagged 2.008 as the latest release.
> The Pro version isn't available anymore. However the new libre version
> is better than the former Pro.
> Even though in the url still says 'pro', in our website we have the
> libre version available instead (we kept the uri for avoiding broken
> links)."
>
>
> Cheers,
> Alex
>
>
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: fonts not working as expected [SOLVED, at least for OP]

[Karlin High]

> On Oct 29, 2018, at 7:20 PM, Karlin High  wrote:
> 
> Glad to hear it's working for you! I'm away from the Mac for 12 hours or so. 
> I'll see what happens when I get back to it.
> -- 
> Karlin High
> Missouri, USA

I got the latest Alegreya font version 2.008 from GitHub, added only the OTF 
font files using FontBook, and restarted the computer. So far, my Mac’s 
LilyPond has not picked up on the Alegreya font. No consequence for me, I don’t 
do production work on this machine. Moving on, unless someone wants some 
additional specific testing done. 
—
Karlin High
Missouri, USA
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: fonts not working as expected

[Alexander Kobel]

On 30/10/2018 14.08, Andrew Bernard wrote:
I have written to huertatipografica to ask where the definitive and most 
current state of Alegreya is to be found, from their website or from 
github. It's not clear what the relationship is between the two.


Hehe, indeed that's a funny coincidence.
Juan Pablo del Peral (the designer) answered just a couple of hours ago 
on https://github.com/huertatipografica/Alegreya/issues/17:


"I just tagged 2.008 as the latest release.
The Pro version isn't available anymore. However the new libre version 
is better than the former Pro.
Even though in the url still says 'pro', in our website we have the 
libre version available instead (we kept the uri for avoiding broken 
links)."



Cheers,
Alex



smime.p7s
Description: S/MIME Cryptographic Signature
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: fonts not working as expected

[Andrew Bernard]

I have written to huertatipografica to ask where the definitive and most
current state of Alegreya is to be found, from their website or from
github. It's not clear what the relationship is between the two.

Andrew
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: fonts not working as expected

[Andrew Bernard]

Hi Kieren,

I tested this carefully on WIndows 10, with lilypond 2.19.82, and Alegreya
Medium from Huerta Tipografica direct. All works fine. The output PDF
according to Acrobat Pro DC shows two fonts from your example,
Alegreya-Medium (Embedded Subset) and TeXGyreSchola-Regular (Embedded
Subset), precisely as expected.

Yet my pristine mac install shows issues.

I don't believe this is a local problem with your computer.

Will report back.
Andrew
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: fonts not working as expected [SOLVED, at least for OP]

[Werner LEMBERG]

> Inspired by Karlin’s comment
> 
>> downloading Alegreya font from GitHub
> 
> I went directly to the source
> () and
> downloaded a new full set from there. (The font set I had before was
> from Google Fonts.)
> 
> Result: All fonts are displaying as expected, in all applications
> **including Lilypond**.
> 
> Conclusion: Not all "Alegreya" fonts are the same!

Oh yes.  Comparing `Alegreya-Medium.ttf': The font available from
Google Fonts is version 2.003 (from October 2017, according to the
`modified' field in the font's `head' table, even if the file stamp
says December 2011) and contains 1344 glyphs.  The new font from the
above link is version 2.007 (generated March 2018) and has 2130
glyphs, coming with a much extended set of OpenType tables.  I also
checked whether the autohinting code (using my ttfautohint program) is
different, but it seems that both fonts were using the same version
since the `fpgm' and `prep' tables are essentially identical.

I've tested various versions of FreeType's `ftview' demo program on my
GNU/Linux box; I can always display both the old and the new font
without problems.  This means that at the most basic level there
doesn't seem to be a fundamental issue.  However, `ftview' doesn't
test the advanced OpenType stuff in the fonts; this gets handled by
Pango and HarfBuzz.

Assuming that the bug is in Pango and/or HarfBuzz: I don't know how
these libraries (as packaged with the lilypond binary) work on the
Mac; maybe they call the native MacOS font engine for font handling.
It is also possible that GNU/Linux versions of Pango and HarfBuzz are
newer, and which have a bug fixed that prevents the use of the old (or
new) Alegreya font.  Another possibility is that `fontconfig' has a
problem, not properly selecting the right Alegreya font from the
family...

With a quite high certainty, however, I can say that the bug is *not*
in lilypond itself.

Regarding problems on the Mac: Are you using TTFs of Alegreya?  Does
it work if you use OTFs instead (available from the Huerta site)?


Werner
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: fonts not working as expected

[Werner LEMBERG]

> I am not a proficient Mac user.  But I recently have one available,
> and decided to have a go.  MacOS Mojave 10.14, LilyPond 2.19.82.  I
> followed the Aaron Hill instructions best as I knew how, downloading
> Alegreya font from GitHub.  Resulting PDF attached.

The attached PDF doesn't contain any Alegreya fonts at all...


Werner

___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: fonts not working as expected [SOLVED, at least for OP]

[Karlin High]

On Mon, Oct 29, 2018 at 6:35 PM Kieren MacMillan <
kieren_macmil...@sympatico.ca> wrote:

> Karlin: If you have a chance, please do the same as I did and report back.
>

Glad to hear it's working for you! I'm away from the Mac for 12 hours or
so. I'll see what happens when I get back to it.
-- 
Karlin High
Missouri, USA
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: fonts not working as expected [SOLVED, at least for OP]

[Kieren MacMillan]

Hi Andrew,

> Does not solve the issue for me! As said, I used the proper font from Huerta 
> Tipografica, as said a while back.
> My Mac was reinstalled pristine especially to test this for you.

In Font Book, do you see all of the Alegreya variants under a single "twisty"? 
Before (when things weren’t working correctly), Font Book had the variants 
listed as three or four separate items; now (with things working), they’re all 
contained under a single "Alegreya" item.

> Is the Mac version of lilypond the neglected step-sister?

That I can’t say…

Cheers,
Kieren.


Kieren MacMillan, composer
‣ website: www.kierenmacmillan.info
‣ email: i...@kierenmacmillan.info


___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: fonts not working as expected [SOLVED, at least for OP]

[Andrew Bernard]

Hi Kieren,

Does not solve the issue for me! As said, I used the proper font from
Huerta Tipografica, as said a while back.

My Mac was reinstalled pristine especially to test this for you.

I normally work on Linux. Is the Mac version of lilypond the neglected
step-sister?

Andrew



On Tue, 30 Oct 2018 at 10:35, Kieren MacMillan <
kieren_macmil...@sympatico.ca> wrote:

> Hi all!
>
> Inspired by Karlin’s comment
>
> > downloading Alegreya font from GitHub
>
> I went directly to the source (<
> https://www.huertatipografica.com/en/fonts/alegreya-ht-pro>) and
> downloaded a new full set from there. (The font set I had before was from
> Google Fonts.)
>
> Result: All fonts are displaying as expected, in all applications
> **including Lilypond**.
>
> Conclusion: Not all "Alegreya" fonts are the same!
>
> Karlin: If you have a chance, please do the same as I did and report back.
>
> Thanks!
> Kieren.
> 
>
> Kieren MacMillan, composer
> ‣ website: www.kierenmacmillan.info
> ‣ email: i...@kierenmacmillan.info
>
>
> ___
> lilypond-user mailing list
> lilypond-user@gnu.org
> https://lists.gnu.org/mailman/listinfo/lilypond-user
>
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: fonts not working as expected

[Andrew Bernard]

It's lilypond it does not work in. Other programs are fine. You need to get
the genuine guaranteed from from Huerta Tipografica ti be sure about all
aspects of the font. It's free to download - very generous for such an
elegant font.

Andrew
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: fonts not working as expected [SOLVED, at least for OP]

[Kieren MacMillan]

Hi all!

Inspired by Karlin’s comment

> downloading Alegreya font from GitHub

I went directly to the source 
() and downloaded a 
new full set from there. (The font set I had before was from Google Fonts.)

Result: All fonts are displaying as expected, in all applications **including 
Lilypond**.

Conclusion: Not all "Alegreya" fonts are the same!

Karlin: If you have a chance, please do the same as I did and report back.

Thanks!
Kieren.


Kieren MacMillan, composer
‣ website: www.kierenmacmillan.info
‣ email: i...@kierenmacmillan.info


___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: fonts not working as expected

[Kieren MacMillan]

Hi all,

Actions Taken
  1.  Removed all Alegreya fonts.
  2.  Restarted computer.
  3.  Reinstalled all Alegreya fonts.
  4.  Launched Lilypond, and cached fonts.

Result:
  1.  In Font Book, all fonts display as expected.
  2.  In LibreOffice (and other text editors), all fonts display as expected.
  3.  In Lilypond, Alegreya Medium [roman and italic] still appears as Alegreya 
Regular, and Alegreya Black [roman] still doesn’t appear at all.

=(

I’ll keep poking around, and report back if I discover anything.

Thanks for trying!
Kieren.


Kieren MacMillan, composer
‣ website: www.kierenmacmillan.info
‣ email: i...@kierenmacmillan.info


___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: fonts not working as expected

[Aaron Hill]

On 2018-10-29 1:40 pm, Kieren MacMillan wrote:

Hi Abraham,

I just downloaded the latest version of Alegreya from the foundry, 
tried your code, and it worked as expected on my Win10 machine.


Is that also true if you use Alegreya Black?

Update: What’s now happening is that using

\override #'(font-name . "Alegreya Medium")

outputs visible markup, styled in Alegreya [Regular] — the base
document font — whereas using

\override #'(font-name . "Alegreya Black")

outputs nothing (i.e., blank where there should be markup). All three
font names appear in Frescobaldi’s auto-complete menu and Lilypond’s
“show available fonts”…


Does the generated PDF show a reference to the font proper?


In all three situations — no override, and with each of the two
overrides seen above — the PDF contains *only* a reference to

/BaseFont/XTCUKI+Alegreya-Regular/FontDescriptor

at least in "clear text".

Ugh…


Probably not what you want to hear but I also am unable to reproduce 
this behavior.



\version "2.19.82"
#(define lorem "Lorem ipsum dolor sit amet, consectetur adipiscing 
elit.")

\markup #lorem
\markup \override #'(font-name . "Alegreya") #lorem
\markup \override #'(font-name . "Alegreya Regular") #lorem
\markup \override #'(font-name . "Alegreya Medium") #lorem
\markup \override #'(font-name . "Alegreya Black") #lorem
\markup \override #'(font-name . "Alegreya Italic") #lorem
\markup \override #'(font-name . "Alegreya Regular Italic") #lorem
\markup \override #'(font-name . "Alegreya Medium Italic") #lorem
\markup \override #'(font-name . "Alegreya Black Italic") #lorem


For reference, I am running 2.19.82 Lilypond under Ubuntu 16.04.4 LTS.  
I downloaded version v2.007 of the fonts from the GitHub [1] and 
manually copied the OTF files to /usr/share/fonts/opentype.


[1]: https://github.com/huertatipografica/Alegreya/releases

I can only recommend that you uninstall the fonts and try reinstalling 
them.  ("Have you tried turning if off and on again?" -- Roy Trenneman, 
IT Crowd)  Perhaps the site where you originally obtained the fonts are 
distributing an older version that has a rare compatibility issue.  It 
could potentially explain why those of us that have tried have not hit 
the issue.


-- Aaron Hill___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: fonts not working as expected

[Kieren MacMillan]

Hey Abraham,

> Well, that is weird. Are you 100% certain Alegreya Medium is showing up as 
> Alegreya Regular? I had to zoom in a fair amount before I could distinguish 
> them clearly.

Here’s the word "harmony" — top is [allegedly, according to the code] Alegreya 
Medium, bottom is Alegreya:


To my eye, they’re identical.

> As for Alegreya Black, that's a complete mystery.

=(

> Possibly an OS problem? I know the recent update to Mojave has been fraught 
> with font changes, but if you haven't updated yet, than that's obviously not 
> a possibility here.

Haven’t updated yet.

I guess I’ll have to push this project out the door some other way…

Thanks,
Kieren.


Kieren MacMillan, composer
‣ website: www.kierenmacmillan.info 
‣ email: i...@kierenmacmillan.info 

___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: fonts not working as expected

[Abraham Lee]

Hey, Kieren!
On Mon, Oct 29, 2018 at 2:40 PM Kieren MacMillan <
kieren_macmil...@sympatico.ca> wrote:

> Hi Abraham,
>
> > I just downloaded the latest version of Alegreya from the foundry, tried
> your code, and it worked as expected on my Win10 machine.
>
> Is that also true if you use Alegreya Black?
>

Yep. Both work for me just fine.


> Update: What’s now happening is that using
>
> \override #'(font-name . "Alegreya Medium")
>
> outputs visible markup, styled in Alegreya [Regular] — the base document
> font — whereas using
>
> \override #'(font-name . "Alegreya Black")
>
> outputs nothing (i.e., blank where there should be markup). All three font
> names appear in Frescobaldi’s auto-complete menu and Lilypond’s “show
> available fonts”…
>

Well, that is weird. Are you 100% certain Alegreya Medium is showing up as
Alegreya Regular? I had to zoom in a fair amount before I could distinguish
them clearly. As for Alegreya Black, that's a complete mystery.


> > Does the generated PDF show a reference to the font proper?
>
> In all three situations — no override, and with each of the two overrides
> seen above — the PDF contains *only* a reference to
>
> /BaseFont/XTCUKI+Alegreya-Regular/FontDescriptor
>
> at least in "clear text".
>
> Ugh…
>

Ugh, indeed. I'm out of ideas on this one since you're specifying
everything correctly in the input file and the font files appear to be
configured correctly. Possibly an OS problem? I know the recent update to
Mojave has been fraught with font changes, but if you haven't updated yet,
than that's obviously not a possibility here.

Best,
Abraham
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: fonts not working as expected

[Kieren MacMillan]

Hi Abraham,

> I just downloaded the latest version of Alegreya from the foundry, tried your 
> code, and it worked as expected on my Win10 machine.

Is that also true if you use Alegreya Black?

Update: What’s now happening is that using

\override #'(font-name . "Alegreya Medium")

outputs visible markup, styled in Alegreya [Regular] — the base document font — 
whereas using

\override #'(font-name . "Alegreya Black")

outputs nothing (i.e., blank where there should be markup). All three font 
names appear in Frescobaldi’s auto-complete menu and Lilypond’s “show available 
fonts”… 

> Does the generated PDF show a reference to the font proper?

In all three situations — no override, and with each of the two overrides seen 
above — the PDF contains *only* a reference to

/BaseFont/XTCUKI+Alegreya-Regular/FontDescriptor

at least in "clear text".

Ugh…
Kieren.


Kieren MacMillan, composer
‣ website: www.kierenmacmillan.info
‣ email: i...@kierenmacmillan.info


___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: fonts not working as expected

[Abraham Lee]

On Mon, Oct 29, 2018 at 9:37 AM Andrew Bernard 
wrote:

> He is using Alegreya Medium.
>
> On Tue, 30 Oct 2018 at 02:17, Abraham Lee 
> wrote:
>
>> Kieren,
>> On Sun, Oct 28, 2018 at 4:28 PM Kieren MacMillan <
>> kieren_macmil...@sympatico.ca> wrote:
>>
>>> Hi Abraham,
>>>
>>> > When you say “outputs nothing” do you mean nothing appears, or nothing
>>> changes from the main doc font?
>>>
>>> It literally disappears — a blank space where there was markup before.
>>>
>>
>> Sounds like a pesky bug, indeed! I'm just curious, does the generated PDF
>> reference the correct font? What is name of the font exactly?
>>
>
Very strange. I just downloaded the latest version of Alegreya from the
foundry, tried your code, and it worked as expected on my Win10 machine. I
looked at the font file's metadata just to see if something was amiss, but
everything seems to be in proper order for maximum cross-platform
compatibility. Sorry I can't be more helpful. Does the generated PDF show a
reference to the font proper?

Best,
Abraham
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: fonts not working as expected

[Andrew Bernard]

He is using Alegreya Medium.

Andrew

On Tue, 30 Oct 2018 at 02:17, Abraham Lee 
wrote:

> Kieren,
> On Sun, Oct 28, 2018 at 4:28 PM Kieren MacMillan <
> kieren_macmil...@sympatico.ca> wrote:
>
>> Hi Abraham,
>>
>> > When you say “outputs nothing” do you mean nothing appears, or nothing
>> changes from the main doc font?
>>
>> It literally disappears — a blank space where there was markup before.
>>
>
> Sounds like a pesky bug, indeed! I'm just curious, does the generated PDF
> reference the correct font? What is name of the font exactly?
>
> Best,
> Abraham
> ___
> lilypond-user mailing list
> lilypond-user@gnu.org
> https://lists.gnu.org/mailman/listinfo/lilypond-user
>
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: fonts not working as expected

[Abraham Lee]

Kieren,
On Sun, Oct 28, 2018 at 4:28 PM Kieren MacMillan <
kieren_macmil...@sympatico.ca> wrote:

> Hi Abraham,
>
> > When you say “outputs nothing” do you mean nothing appears, or nothing
> changes from the main doc font?
>
> It literally disappears — a blank space where there was markup before.
>

Sounds like a pesky bug, indeed! I'm just curious, does the generated PDF
reference the correct font? What is name of the font exactly?

Best,
Abraham
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: fonts not working as expected

[Andrew Bernard]

I have freshly installed Mac OS 10.13.6 HIgh Sierra. Using lilypond
2.19.80, when specifying "Alegreya Medium" as the font name, whether the
font is installed system wide for for just me, the example compiles but the
Alegreya reverts to the lilypond sans default. Definitely not working
right. And I cleared the lilypond font cache before starting.

\version "2.19.80"
\markup "test"
\markup \override #'(font-name . "Alegreya Medium") "test"


Andrew
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: fonts not working as expected

[Andrew Bernard]

Hi Kieran,

In a message to me you mentioned you are using Alegreya Medium. Downloading
this from the original type foundry, with 2.19.82 on Ubuntu 18.10 the use
of the font name "Alegreya Medium", just that, works just fine.

I'll try it on my Mac.

Andrew
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: fonts not working as expected

[Kieren MacMillan]

Hi Abraham,

> When you say “outputs nothing” do you mean nothing appears, or nothing 
> changes from the main doc font?

It literally disappears — a blank space where there was markup before.

Thanks,
Kieren.


Kieren MacMillan, composer
‣ website: www.kierenmacmillan.info
‣ email: i...@kierenmacmillan.info


___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: fonts not working as expected

[Abraham Lee]

Hey, Kieren!

On Sun, Oct 28, 2018 at 2:13 PM Kieren MacMillan <
kieren_macmil...@sympatico.ca> wrote:

> Hi all,
>
> No MWE possible, because obviously it’s a local problem with my computer…
>
> I’ve installed fonts on my computer. I’ve restarted the machine, and
> allowed Lilypond to recache fonts. Frescobaldi’s auto-completion mechanism
> recognizes (and suggests) the new fonts, and they appear as expected in
> Font Book, they show up when I run '-dshow-available-fonts x', etc.
>
> So they seem to be installed properly, and recognized by the various
> applications involved. But
>
>   \markup "test"
>
> outputs as expected [using the main document font], whereas
>
>   \markup \override #'(font-name . "New Font Name") "test"
>
> outputs nothing.
>
> What should I be looking for to fix this problem? How can I debug it
> further to see what’s wrong?


When you say “outputs nothing” do you mean nothing appears, or nothing
changes from the main doc font?

Best,
Abraham

>
>
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user