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

> 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

Re: fonts not working as expected

> 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 contai

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

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. -- Kar

Re: Direction operators in event-function

David Kastrup writes: > Urs Liska writes: > >> But if I simply create two elements in the event-function the explicit >> direction operator takes no effect: >> >> propagate-direction = >> #(define-event-function (text)(markup?) >>#{ >> -( >> -\markup #text >>#}) >> >> { >> g'

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

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 we

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

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 Oc

Re: fonts not working as expected

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-

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

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 displayi

Re: version 2.18 is too old...

Am 29.10.2018 um 17:25 schrieb Mike Dean: For what it's worth, following are two bug reports Frescobaldi auto-emailed... Traceback (most recent call last):   File "C:\Program Files (x86)\Frescobaldi\frescobaldi_app\process.py", line 105, in _done     del self._schedule[0] IndexError: list a

Re: fonts not working as expected

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 expecte

Re: Line-breaking with non-aligned barlines

-Original Message- From: Thomas Morley To: David Sumbler CC: lilypond-user Subject: Re: Line-breaking with non-aligned barlines Date: Mon, 29 Oct 2018 22:25:42 +0100 Am Mo., 29. Okt. 2018 um 12:10 Uhr schrieb David Sumbler < da...@aeolia.co.uk>: > > > -Original Message- > Fr

Re: fonts not working as expected

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

Re: fonts not working as expected

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: T

Re: Line-breaking with non-aligned barlines

Am Mo., 29. Okt. 2018 um 12:10 Uhr schrieb David Sumbler : > > > -Original Message- > From: Thomas Morley > To: David Sumbler > CC: lilypond-user > Subject: Re: Line-breaking with non-aligned barlines > Date: Sun, 28 Oct 2018 02:01:04 +0200 > > Am Fr., 26. Okt. 2018 um 23:52 Uhr schrieb

Re: fonts not working as expected

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 B

Re: fonts not working as expected

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 vi

Re: Use a variable Scheme module

Am 29.10.2018 um 14:54 schrieb David Kastrup: Urs Liska writes: Is there a way (well, I think I should ask: what's the way) to use Scheme modules whose names are only available at runtime? (use-modules (root-level my-module)) where my-module might change. What I actually want to achieve i

Re: fonts not working as expected

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 “outpu

Re: version 2.18 is too old...

Am 29.10.18 um 17:05 schrieb Mike Dean: 1. Yes, it did […] On Mon, Oct 29, 2018 at 12:01 PM Sam Bivens > wrote: Hi Mike, Does your version statement in the file youre compiling say 2.18.2? Sam Then you probably included a file which contains a

Re: version 2.18 is too old...

For what it's worth, following are two bug reports Frescobaldi auto-emailed... Traceback (most recent call last): File "C:\Program Files (x86)\Frescobaldi\frescobaldi_app\process.py", line 105, in _done del self._schedule[0] IndexError: list assignment index out of range Traceback (most rec

Re: version 2.18 is too old...

Hi Mike, Does your version statement in the file youre compiling say 2.18.2? Sam On Mon, Oct 29, 2018, 11:55 Mike Dean wrote: > Error message: > > Starting lilypond-windows.exe 2.18.2 [May-Jesus-Christ-Be-Praised.ly]... > > Processing > `C:/Users/Mike/Documents/musicwork/May-Jesus-Christ-Be-P

Re: fonts not working as expected

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

Re: version 2.18 is too old...

1. Yes, it did Having downloaded LilyPond 2,19.82, the compilation attempt 'crashed and burned' at the start: Starting lilypond-windows.exe [May-Jesus-Christ-Be-Praised.ly]... Exited with return code -1073741819. Mike Dean On Mon, Oct 29, 2018 at 12:01 PM Sam Bivens wrote: > Hi Mike, > > Doe

Re: version 2.18 is too old...

Whether version 2.18 is ‘too old’ or not, depends entirely on the input file. That's merely the message Lily gives according to the \version statement in the input. But indeed, the unstable version provide a lot of advantages over the quite old stable one (a new one is due pretty soon-ish) while

version 2.18 is too old...

Error message: Starting lilypond-windows.exe 2.18.2 [May-Jesus-Christ-Be-Praised.ly]... Processing `C:/Users/Mike/Documents/musicwork/May-Jesus-Christ-Be-Praised.ly' Parsing... error: program too old: 2.18.2 (file requires: 2.20.0) Would version 2.19.82 be a workaround? Mike Dean _

Re: fonts not working as expected

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. >

Re: Use a variable Scheme module

Maybe I'm on the wrong track altogether, so I restart by stating more generally what I want to achieve. For Jan-Peter's lilypond-export package (the same can probably be applied later to the export-targets of scholarLY annotations) export functions for various formats are/will be implemented i

Re: purple highlight in Frescobaldi

Thanks-in my case it was Ctrl-B instead of Ctrl-V. Sent from my iPhone > On Oct 27, 2018, at 3:26 AM, Urs Liska wrote: > > > > Am 27. Oktober 2018 08:59:30 MESZ schrieb Andrew Bernard > : >> Hello Joseph, >> >> Something that tricked me for a long time also. Many people don't >> realize >>

A few questions about Scheme functions

I have a few questions about using Scheme to build Lilypond data. 1. I have some Scheme code that builds custom articulations (more precisely, it attaches metadata to NoteEvents, and the only way I found to make this possible is via putting it in a custom, invisible articulation, but let's not dig

A few questions about Scheme functions

I have a few questions about using Scheme to build Lilypond data. 1. I have some Scheme code that builds custom articulations (more precisely, it attaches metadata to NoteEvents, and the only way I found to make this possible is via putting it in a custom, invisible articulation, but let's not dig

Three questions about Scheme functions

I have a few questions about using Scheme to build Lilypond data. 1. I have some Scheme code that builds custom articulations (more precisely, it attaches metadata to NoteEvents, and the only way I found to make this possible is via putting it in a custom, invisible articulation, but let's not dig

Re: Use a variable Scheme module

Am 29.10.2018 um 14:54 schrieb David Kastrup: Urs Liska writes: Is there a way (well, I think I should ask: what's the way) to use Scheme modules whose names are only available at runtime? (use-modules (root-level my-module)) where my-module might change. What I actually want to achieve i

Re: Use a variable Scheme module

Urs Liska writes: > Is there a way (well, I think I should ask: what's the way) to use > Scheme modules whose names are only available at runtime? > > (use-modules (root-level my-module)) > > where my-module might change. What I actually want to achieve is load > all modules for which .scm files

Use a variable Scheme module

Is there a way (well, I think I should ask: what's the way) to use Scheme modules whose names are only available at runtime? (use-modules (root-level my-module)) where my-module might change. What I actually want to achieve is load all modules for which .scm files are found in a directory. A

Re: Line-breaking with non-aligned barlines

-Original Message- From: Thomas Morley To: David Sumbler CC: lilypond-user Subject: Re: Line-breaking with non-aligned barlines Date: Sun, 28 Oct 2018 02:01:04 +0200 Am Fr., 26. Okt. 2018 um 23:52 Uhr schrieb David Sumbler < da...@aeolia.co.uk>: > But as things are the break here is

Re: Line-breaking with non-aligned barlines

Am Mo., 29. Okt. 2018 um 07:58 Uhr schrieb Werner LEMBERG : > > > >> If possible, this should be made the default. I even suggest to > >> completely drop the current behaviour since I can't envision a > >> situation where you really want this. > > > > I'll open an issue on the tracker. > > Thanks.

Re: \RemoveEmptyStaves not removing first line

Am 29.10.18 um 05:52 schrieb Lukas-Fabian Moser: I am currently engraving a song for soprano and piano which begins with 15 measures of piano solo. I would like the soprano's staff not to show since it is not playing. \RemoveEmptyStaves does not seem to hide the first line of the piece.