Lilypond ships with a text font as well as a music font. I agree that I
suspect that currently Lilypond's text font does not actually define these
Unicode music characters, so it falls back on the OS to find them. Why not
just add copies of Emmentaler glyphs to the Lilypond text fonts for
> IMO Lilypond should render musical Unicode characters using the same
> font as the music itself,
No, it should not. If you select font 'foo' for text rendering,
everything should come from that font. If a certain character is not
in 'foo', it is the FontConfig library rather than LilyPond
IMO Lilypond should render musical Unicode characters using the same font
as the music itself, and the default size/alignment of the glyphs within
text markup should not require adjustment to look correct.
On Sun, Jan 15, 2023 at 4:07 AM William Rehwinkel <
will...@williamrehwinkel.net> wrote:
>
Dear list,
When I use a lilypond file structured similarly to the following minimal
example, I get a programming error message thrown when compiling:
programming error: found a page-turnable place which was not breakable
The resulting file does look correct, with the bookparts seperated and
> On 15 Jan 2023, at 23:30, Jean Abou Samra wrote:
>
> Le 16/01/2023 à 00:21, Graham King a écrit :
>>
>> My first steps into recent versions of lilypond are ruthlessly exposing my
>> ignorant copy-&-paste approach to scheme...
>>
>> I'm pretty sure that the following code worked fine
Le 16/01/2023 à 00:21, Graham King a écrit :
My first steps into recent versions of lilypond are ruthlessly
exposing my ignorant copy-&-paste approach to scheme...
I'm pretty sure that the following code worked fine under lilypond
2.18, but throws errors under 2.25.0:
\version "2.25.0"
%
My first steps into recent versions of lilypond are ruthlessly exposing
my ignorant copy-&-paste approach to scheme...
I'm pretty sure that the following code worked fine under lilypond 2.18,
but throws errors under 2.25.0:
\version "2.25.0"
% gitver and gitrev (from
On 2023-01-15 19:30, Jean Abou Samra wrote:
Le 15/01/2023 à 20:20, Graham King a écrit :
I've just run convert-ly on a 600+ line file and its \include files,
from 2.19.40 to 2.25.0. Nothing seemed to change apart from the
\version statement, but on trying to compile the file, I get:
Dear Paul,
Assuming that the symbol is a marcato-staccato, one could use some
scheme code a bit like the following which is pasted together from the
short fermata and staccato definitions, so that the layout and midi
outputs are properly handled.
-William
\version "2.24.0"
I forgot the second part of the question:
Le 15/01/2023 à 20:20, Graham King a écrit :
Before I start laboriously bisecting the file, is there a way to get an error
message that points to one or more lines of code in the file?
Try
#(ly:set-option 'compile-scheme-code)
(Caveat: not
Le 15/01/2023 à 20:20, Graham King a écrit :
I've just run convert-ly on a 600+ line file and its \include files, from
2.19.40 to 2.25.0. Nothing seemed to change apart from the \version statement,
but on trying to compile the file, I get:
Processing `/tmp/ly'
Parsing...ERROR: In
I've just run convert-ly on a 600+ line file and its \include files, from
2.19.40 to 2.25.0. Nothing seemed to change apart from the \version statement,
but on trying to compile the file, I get:
Processing `/tmp/ly'
Parsing...ERROR: In procedure %resolve-variable:
Unbound variable: %
Dear Saul,
I don't see why this would be surprising... as you said it's the
difference of using the unicode symbol from the text font (such as
unicode symbol https://www.compart.com/en/unicode/U+266D for a flat) for
an accidental and pasting in the lilypond musical font symbol for that
This is simply a combination of marcato (aka "strong accent") and staccato.
The symbols are not usually overlapped like that, but it is not unknown - see
the attached image from "Music Engraving Today" by Steven Powell (which I found
in a discussion of how to get Dorico to do this).
I
14 matches
Mail list logo
