Thank you, Jean. Of course! The broader issue for me is that I hadn't
grasped that it was actually a << {...} \\ {...} >> construction in the
newer, simpler format.
I'm so grateful for your help. I was going around in circles, knowing
that the solution had to be something straightforward.
> I've tried placing the new bar in 3 different places on the treble
> staff. In the current pdf, the first 2 are commented out and the third
> -- which I expected to work -- is active: placement after the >>.
> Somehow a spurious bar is inserted, but I don't know where it's coming from.
Thank you all ... I learned a lot fromt your answers Now I just have to
implement a solution.
Greetings
Morten
Lukas-Fabian Moser skrev den 2024-05-11 16:32:
Here’s one approach:
%%% SNIPPET BEGINS
\version "2.25.11"
esp = \markup \lower #1 \scale #'(1.375 . 1) \musicglyph
#"scripts.espr"
:
On 12/05/2024 12:41, Archer Endrich wrote:
Hello,
I've been given a short item to realise in Lilypond and it includes a
layout problem that I haven't been able to solve.
Basically, it is a piano piece in which, after a bit, a part for
chimes is added: i.e., another staff above the piano's treble
On 12/05/2024 12:41, Archer Endrich wrote:
Hello,
I've been given a short item to realise in Lilypond and it includes a
layout problem that I haven't been able to solve.
Basically, it is a piano piece in which, after a bit, a part for
chimes is added: i.e., another staff above the piano's
Hello,
I've been given a short item to realise in Lilypond and it includes a
layout problem that I haven't been able to solve.
Basically, it is a piano piece in which, after a bit, a part for chimes
is added: i.e., another staff above the piano's treble part a few bars
in as in my MWE. I
Here’s one approach:
%%% SNIPPET BEGINS
\version "2.25.11"
esp = \markup \lower #1 \scale #'(1.375 . 1) \musicglyph #"scripts.espr"
stuff = \relative {
\time 4/4
r4 b'4 a2-\tweak self-alignment-X #-1.25 _\esp ~
a2 b4 4(
c1)-\tweak self-alignment-X #-0.5 _\esp
Hi Mats,
> On May 11, 2024, at 11:51 AM, Mats Bengtsson wrote:
> I would rather do something like the following
I started down that path, but when I saw that the output was
I realized it would take far too much manual tweaking to make it visually
attractive, whereas my \esp version gives
On 2024-05-11 15:18, Kieren MacMillan
wrote:
Hi Morten,
Here’s one approach:
%%% SNIPPET BEGINS
\version "2.25.11"
esp = \markup \lower #1 \scale #'(1.375 . 1) \musicglyph #"scripts.espr"
stuff = \relative {
\time 4/4
r4 b'4 a2-\tweak
Hi Morten,
Here’s one approach:
%%% SNIPPET BEGINS
\version "2.25.11"
esp = \markup \lower #1 \scale #'(1.375 . 1) \musicglyph #"scripts.espr"
stuff = \relative {
\time 4/4
r4 b'4 a2-\tweak self-alignment-X #-1.25 _\esp ~
a2 b4 4(
c1)-\tweak self-alignment-X #-0.5 _\esp
mor...@borchorst.eu skrev den 2024-05-11 11:40:
Dear list
I am trying to solve this problem about espressivos that stretches
over four beats. I have tried many versions but not seems to solve it
The c1 and the b4 c2 b4 bars work as I hoped for.
the b2 c2 bar and the a2~ a2 does not give
Dear list
I am trying to solve this problem about espressivos that stretches
over four beats. I have tried many versions but not seems to solve it
The c1 and the b4 c2 b4 bars work as I hoped for.
the b2 c2 bar and the a2~ a2 does not give the wished for results.
Can anybody help
On Wed, May 1, 2024 at 10:55 PM Robert Garrigos wrote:
> Oh this is a bit embarrassing, such a basic error….. sorry, I never
> realized that the parenthesis needs to be right after the first note.
>
Nothing to be embarrassed about. It takes some getting used to.
--
Knute Snortum
; Sent: Wednesday, May 1, 2024 2:15 PM
> To: Robert Garrigos ; LilyPond Users
>
> Subject: Re: slurs problem with voices
>
> On 01/05/2024 21:57, Robert Garrigos wrote:
>>
>> Why is not the first example working? I tried with explicit voicing with the
>> same
024 2:15 PM
To: Robert Garrigos ; LilyPond Users
Subject: Re: slurs problem with voices
On 01/05/2024 21:57, Robert Garrigos wrote:
Why is not the first example working? I tried with explicit voicing with the
same results.
Thanks.
Robert
The slur starts at the d2 so must be placed wi
On Wed, May 1, 2024 at 1:59 PM Robert Garrigos wrote:
> I have this music to engrave, note the slur:
> [...]
> Why is not the first example working? I tried with explicit voicing with
> the same results.
>
Slurs in LilyPond are "post events", meaning they always go *after* the
note. So if you
On 01/05/2024 21:57, Robert Garrigos wrote:
Why is not the first example working? I tried with explicit voicing with the
same results.
Thanks.
Robert
The slur starts at the d2 so must be placed with that note following the
pitch and duration,
{ d4 d2( | \hideNotes ef8)}
--
Timothy
Hi Robert,
> I tried different approaches but cannot get that slur.
\version "2.25.14"
\language "english"
global = {
\key ef \minor
\time 3/4
}
\relative c' {
\clef treble
\global
<<
{ bf'4 cf2 \tweak staff-position #5.1 ~ | 8 8 r8 r8 }
\\
{ d4 d2( | \hideNotes ef8) }
I have this music to engrave, note the slur:
I tried different approaches but cannot get that slur. This is my code, with
two examples:
\version "2.25.14"
\language "english"
global = {
\key ef \minor
\time 3/4
}
first_example = \relative c' {
\clef treble
\global
<<
{bf'4 \once
Thank you Xavier!
You gave me the hint I needed.
I need to specify that the text spanner should start below (not
default, which is above).
Problem solved.
Ken
On Mon, Apr 22, 2024 at 1:18 PM Xavier Scheuer wrote:
>
> On Mon, 22 Apr 2024 at 21:48, Kenneth Wolcott
> wrote:
&
On Mon, 22 Apr 2024 at 21:48, Kenneth Wolcott
wrote:
>
> Hi;
>
> I've made a simple mistake but I can't figure out what I did wrong.
>
> At bar #36 the first text spanner starts. I think that's correct. But
> the piano articulation should be a bar earlier? But that also seems
> correct. How
On Sat, Mar 16, 2024 at 10:20 AM Hans Aikema
wrote:
>
>
> On 16 Mar 2024, at 17:49, Phil Holmes wrote:
>
> Very short hairpins?
>
> Phil
>
> On 16/03/2024 16:27, Ralph Palmer wrote:
>
> Hi, Again -
>
> I've searched the Notation documentation and the LSR, and I cannot figure
> out how to solve
> On 16 Mar 2024, at 17:49, Phil Holmes wrote:
>
> Very short hairpins?
>
> Phil
>
> On 16/03/2024 16:27, Ralph Palmer wrote:
>> Hi, Again -
>>
>> I've searched the Notation documentation and the LSR, and I cannot figure
>> out how to solve this. It looks like a half note with an accent
Very short hairpins?
Phil
On 16/03/2024 16:27, Ralph Palmer wrote:
Hi, Again -
I've searched the Notation documentation and the LSR, and I cannot
figure out how to solve this. It looks like a half note with an accent
followed by a half note with the opposite figure. (You may have to
zoom
Hi, Again -
I've searched the Notation documentation and the LSR, and I cannot figure
out how to solve this. It looks like a half note with an accent followed by
a half note with the opposite figure. (You may have to zoom in a bit!) I
can do the accent, and I seem to remember its opposite, but I
Jean and Kieren -
Thank you both for pointing me in the right direction. Kieren, I actually
looked at Visibility of Objects, but somehow did not see \undo.
All the best,
Ralph
__
Ralph Palmer
Seattle
USA
(he, him, his)
palmer.r.vio...@gmail.com
On Tue, Mar 12, 2024 at 7:51 AM Kieren
Hi Ralph,
> I cannot figure out how to revert or reverse "\omit TupletNumber". "\once
> \omit TupletNumber" does, in fact omit only the next tuplet number. However,
> if I use "\omit TupletNumber", it omits all folowing tuplet numbers, and I
> cannot find a command to restore the tuplet
> I cannot figure out how to revert or reverse "\omit TupletNumber".
\undo \omit TupletNumber
Best,
Jean
signature.asc
Description: This is a digitally signed message part
Hello, again -
I cannot figure out how to revert or reverse "\omit TupletNumber". "\once
\omit TupletNumber" does, in fact omit only the next tuplet number.
However, if I use "\omit TupletNumber", it omits all folowing tuplet
numbers, and I cannot find a command to restore the tuplet numbers. Any
Thanks, Kieren -
Yes. My mistake. Still didn't quite do what I'd hoped, though, even when I
corrected it.
All the best,
Ralph
__
Ralph Palmer
Seattle
USA
(he, him, his)
palmer.r.vio...@gmail.com
On Wed, Mar 6, 2024 at 7:42 PM wrote:
> Hi Ralph,
>
> Shouldn’t the d be 4. [not 4]?
>
> >
:8 } c4.*2/3:8 d4.*2/3:8 | c2.*2/3:8 b4.*2/3:8
> a4.*2/3:8
> }
>
> -William
>
> On 3/6/24 21:53, Ralph Palmer wrote:
> > Hi -
> >
> > Thanks for all your work and for your help to me over a number of years.
> >
> > I'm running into a problem I hav
d for your help to me over a number of years.
I'm running into a problem I have no idea how to fix. I've looked at
tremolos in the Notation Reference and in the Snippet Repository, but
can't find a solution. I would appreciate any help. The first image is
the result of tremoloTripletProblem.ly.
Hi Ralph,
Shouldn’t the d be 4. [not 4]?
bf2.:6 c4.:3 d4:3 |
Maybe I’m misunderstanding…?
Cheers,
Kieren.
Hi -
Thanks for all your work and for your help to me over a number of years.
I'm running into a problem I have no idea how to fix. I've looked at
tremolos in the Notation Reference and in the Snippet Repository, but can't
find a solution. I would appreciate any help. The first image
Hi lilyponders!
I have a problem with a frenched score. From a larger piece I'm creating
an excerpt for the choir and that shall be "frenched", aka voices that
have nothing to do are removed while they are silent.
As documented this is nicely done when I add a
\RemoveAllE
to this problem.
The user only needs to enter pedal settings at the beginning of a passage,
which looks like:
<>\setHarpPedals { d c b e f g a }
Harp_pedal_engraver then listens for notes and automatically prints pedal
changes when new accidentals occur. Manually entered pedal changes
That worked perfectly:
Emacs > Options > Customize Emacs > Options Matching > Lilypond > Lilypond
Lilypond Command > /usr/bin/lilypond
--include=/home/laurie/Lilypond/includes "${@}"
Thanks
Laurie Savage
https://www.queensofthewest.com/
The Latest Queens of The West clips
Laurie Savage wrote on 13.11.2023:
> Still I get errors like this:
> /home/laurie/Documents/Charts/Transpositions/Dear Old
> Stockholm/Dear-Old-Stockhom_Traditional.ly:3:10: error: cannot find file:
> `/home/Laurie/Lilypond/includes/jazzchords.ily'
>
> ...
>
> Any ideas?
I am not calling
Thanks for trying!
Laurie Savage
On Tue, 14 Nov 2023 at 20:59, David Kastrup wrote:
> Laurie Savage writes:
>
> > Thanks David,
> >
> > I think I'll stay with Frescobaldi! Emacs doesn't seem to edit .ly files
> > any more easily so there isn't much advantage in tweaking it to behave
> with
> >
Laurie Savage writes:
> Thanks David,
>
> I think I'll stay with Frescobaldi! Emacs doesn't seem to edit .ly files
> any more easily so there isn't much advantage in tweaking it to behave with
> my customised Include files. As for your question about where I found the
> documentation for the
Thanks David,
I think I'll stay with Frescobaldi! Emacs doesn't seem to edit .ly files
any more easily so there isn't much advantage in tweaking it to behave with
my customised Include files. As for your question about where I found the
documentation for the location of my Includes: Options >
On Tue 14 Nov 2023 at 07:04:39 (+1100), Laurie Savage wrote:
> Thanks, I should have spotted that.
So presumably the "cannot find file" error went away when you
corrected the full path "/home/Laurie/Lilypond/includes/jazzchords.ily"
but how about when you type only:
\include "jazzchords.ily"
Thanks, I should have spotted that. But I'm not sure why this setting
hasn't been picked up by Emacs lilypond mode:
Lilypond Include Path: String: /home/laurie/Lilypond/includes
State : SAVED and set.
LilyPond include path.
Groups: Lilypond
I don't want to type the full file path
On Mon, Nov 13, 2023 at 02:45:26PM +1100, Laurie Savage wrote:
>I store my Includes file in a directory ~/Lilypond/includes but
>Lilypond mode cannot locate them even if I specify a full file name e.g
>\include
>"/home/Laurie/Lilypond/includes/jazzchords.ily"
>I set this in my
Hi,
I thought I'd give the Emacs Lilypond mode a try-out. I like Emacs and have
used it a lot for coding and writing in LaTeX in my past career. (No editor
wars please, VIM is good too but I'm less familiar with it!)
I store my Includes file in a directory ~/Lilypond/includes but Lilypond
mode
Thanks Jean, that worked!
It was a bigger drama than I expected--just about everything I can access
on this laptop (it's my work machine) is linked to the OneDrive folder,
meaning that silly bracket turned up everywhere. I managed to find a
high-level (and safe) folder to move it to though, and
Ouch, I think I see the cause. Could you move LilyPond to a folder whose full
path doesn't contain any parentheses and retry?
signature.asc
Description: This is a digitally signed message part
Apologies for not including the list--my usual client does that default,
but I'm not using my usual client!
Here's the .ly file as requested.
Cameron Horsburgh
On Wed, 11 Oct 2023 at 13:14, Jean Abou Samra wrote:
> Le mercredi 11 octobre 2023 à 13:03 +1030, Cameron Horsburgh a écrit :
>
>
Hi,
That is a weird problem. Could you run LilyPond with the --ps option and send
the resulting PostScript file?
Thanks,
Jean
signature.asc
Description: This is a digitally signed message part
Hi all,
I've got LilyPond 2.24.2 running on Windows 11. It's installed as a local
installation in a folder in my OneDrive folder and I've never had a problem
with this setup before. My problem has only appeared since moving to a
Windows 11 machine though, so that might be relevant, although I
Thank you. It worked. С уважением,Виноградов Юрий.10.10.2023, 21:31, "Jean Abou Samra" :Le mardi 10 octobre 2023 à 21:16 +0300, Виноградов Юрий a écrit :Hello. Please help me to remove this collision at the beginning of the piece. So that everything starts smoothly.You need to insert grace skips
Le mardi 10 octobre 2023 à 21:16 +0300, Виноградов Юрий a écrit :
> Hello. Please help me to remove this collision at the beginning of the piece.
> So that everything starts smoothly.
You need to insert grace skips (“\grace { s8 }”) in each staff that does not
start with a grace note.
See
The oldest bug of all, I believe!
Just put hidden ("s") appoggiaturas in the other parts and then everything will
line up.
Paul
From: Виноградов Юрий
To: "lilypond-user@gnu.org"
Sent: 10/10/2023 19:16
Subject: The problem of acciaccatura from the b
Hello. Please help me to remove this collision at the beginning of the piece. So that everything starts smoothly. С уважением,Виноградов Юрий.
Graham King writes:
> Many thanks David!
>
> (In the course of trying to convert the \note syntax, I discovered the
> existence of \note-by-number which solved 90% of my problem. Sorry for
> the confusing reference to \note.)
Well, \note-by-number #1 #0 #UP is essentially the s
Many thanks David!
(In the course of trying to convert the \note syntax, I discovered the
existence of \note-by-number which solved 90% of my problem. Sorry for
the confusing reference to \note.)
On Sun, 2023-09-17 at 00:38 +0200, David Kastrup wrote:
> Graham King writes:
>
> >
Graham King writes:
> I'm trying to convert a naive Scheme function which has been broken by
> the new syntax for \note. Some arithmetic gives me the index (in this
> MNWE, 96) to a list of pairs, foo, from which I want to extract some
> markup.
>
> The 300-LOC problem
I'm trying to convert a naive Scheme function which has been broken by
the new syntax for \note. Some arithmetic gives me the index (in this
MNWE, 96) to a list of pairs, foo, from which I want to extract some
markup.
The 300-LOC problem seems to boil down
> On Aug 27, 2023, at 11:55 PM, Werner LEMBERG wrote:
>
>
>>>> I do not think that my Times New Roman font is corrupted.
>>
>> Actually, I think it is: Most likely the font's 'post' table is
>> broken (i.e., it has a wrong PostScript name for glyph 'N').
> On 28 Aug 2023, at 08:49, Jean Abou Samra wrote:
>
>
>
>> Le 28 août 2023 à 08:45, Jean Abou Samra a écrit :
>>
>>
>>
>>> You might try to copy the affected font from macOS 14 to macOS 13 and
>>> check whether it works.
>>
>>
>> This bug has already been fixed in Homebrew. Please
> Le 28 août 2023 à 08:45, Jean Abou Samra a écrit :
>
>
>
>> You might try to copy the affected font from macOS 14 to macOS 13 and
>> check whether it works.
>
>
> This bug has already been fixed in Homebrew. Please just uninstall and
> reinstall LilyPond and it should go away.
> You might try to copy the affected font from macOS 14 to macOS 13 and
> check whether it works.
This bug has already been fixed in Homebrew. Please just uninstall and
reinstall LilyPond and it should go away.
Jean
> Jean did the analysis then, he can tell more.
D'oh, *I* did the analysis then :-)
https://gitlab.com/lilypond/lilypond/-/issues/6508
Werner
>>> I do not think that my Times New Roman font is corrupted.
>
> Actually, I think it is: Most likely the font's 'post' table is
> broken (i.e., it has a wrong PostScript name for glyph 'N').
> Normally, you won't see the problem at all because most applications
> acce
>> I am experiencing a very weird problem with Lilypond on macOS 13
>> Ventura. When using the Times New Roman font, the capital letter N
>> is mis-printed.
Have a look at the thread starting at
https://lists.gnu.org/archive/html/lilypond-user/2022-12/msg00349.html
whic
Hi.
> On 28 Aug 2023, at 11:36, David F. wrote:
>
> I am experiencing a very weird problem with Lilypond on macOS 13 Ventura.
> When using the Times New Roman font, the capital letter N is mis-printed.
>
I can confirm and replicate this under 13.4.1
> I do not think that
Thank you Jean!
On Sat, May 13, 2023 at 7:19 AM Jean Abou Samra wrote:
>
> Le vendredi 12 mai 2023 à 20:42 -0700, Kenneth Wolcott a écrit :
>
> Hi;
>
> I'm converting a 2.22.2 Lilypond engraving where I manually implemented a
> fine+dc_al_fine repeat into a 2.24.1 repeat segno and I run into
Le vendredi 12 mai 2023 à 20:42 -0700, Kenneth Wolcott a écrit :
> Hi;
>
> I'm converting a 2.22.2 Lilypond engraving where I manually
> implemented a fine+dc_al_fine repeat into a 2.24.1 repeat segno and I
> run into difficulties.
>
> Since the fine ends at beat 3 of 4 (well, 2/2 meter), I
Forgot to include screenshots of the origin that I'm using as a sample
to engrave from...
On Fri, May 12, 2023 at 8:42 PM Kenneth Wolcott
wrote:
>
> Hi;
>
> I'm converting a 2.22.2 Lilypond engraving where I manually
> implemented a fine+dc_al_fine repeat into a 2.24.1 repeat segno and I
> run
Hi;
I'm converting a 2.22.2 Lilypond engraving where I manually
implemented a fine+dc_al_fine repeat into a 2.24.1 repeat segno and I
run into difficulties.
Since the fine ends at beat 3 of 4 (well, 2/2 meter), I run into
issues with partials and bar checks.
I also run into problems with
n
> and reinstalling with the same result. I tried some other old versions, and
> this is the only version that has this problem. Is it an interaction with
> Windows 11, perhaps (which I upgraded to recently)?
That's possible. I also started to get this problem with an upgrad
Exited with return code -1073741819.
I'm sure this has been OK in the past, and I even tried downloading it again
and reinstalling with the same result. I tried some other old versions, and
this is the only version that has this problem. Is it an interaction with
Windows 11, perhaps (which I
>> [...] after doing a grep over the git repository, which leads me to
>> `property-iterator.cc`, it's not really clear to me what's going
>> on...
>
> Well, you can find it in `define-event-classes.scm`. It's the event
> class for events created by `\override`s.
Ah, yes, I missed that while
Le jeudi 16 février 2023 à 06:30 +, Werner LEMBERG a écrit :
> ```
>
> >> As can be seen, the acciaccatura neither has a slash nor a slur if
> >> quoted. [...]
> >
> > This looks like a real bug, please file an issue.
>
>
>> As can be seen, the acciaccatura neither has a slash nor a slur if
>> quoted. [...]
>
> This looks like a real bug, please file an issue.
https://gitlab.com/lilypond/lilypond/-/issues/6531
> AFAICS, this works:
>
> ```
> \version "2.25.2"
>
> \layout {
> \context {
> \Score
>
Le mercredi 15 février 2023 à 19:34 +, Werner LEMBERG a écrit :
> ```
>
> Consider this example.
>
> ```
> fluteNotes = \relative {
> r2. c''4 |
> d8 \acciaccatura e c d e fis2 |
> g2 d |
> }
>
> oboeNotes = \relative c'' {
> R1 |
> \cueDuring "flute" #UP { R1 } |
> g2 d |
> }
>
Consider this example.
```
fluteNotes = \relative {
r2. c''4 |
d8 \acciaccatura e c d e fis2 |
g2 d |
}
oboeNotes = \relative c'' {
R1 |
\cueDuring "flute" #UP { R1 } |
g2 d |
}
\addQuote "flute" { \fluteNotes }
<<
\new Staff \fluteNotes
\new Staff \oboeNotes
>>
```
As can be
Jean Abou Samra writes:
> Le lundi 13 février 2023 à 18:08 +0100, David Kastrup a écrit :
>> That begs the question whether it would make sense to restrict
>> afterGrace scales to values below 1. But I think that making syntactic
>> decisions based on values rather than types is really
Le lundi 13 février 2023 à 18:08 +0100, David Kastrup a écrit :
> That begs the question whether it would make sense to restrict
> afterGrace scales to values below 1. But I think that making syntactic
> decisions based on values rather than types is really icky. It is
> probably a bad
Lukas-Fabian Moser writes:
> Hi Werner,
>
>>> Alternatively you may try to use \afterGrace to insert the \clef
>>> before the bar line, although this would probably require some
>>> manual spacing too.
>> This doesn't work at all: `\afterGrace` doesn't accept a clef, as the
>> image shows.
>
>
> That is because you are using 1 instead of a note name such as c'1. after-
> grace does not handle this mechanism.
Thanks (and thanks to Lukas, too)!
> Instead of manually extra-offsetting the Clefs you might also do
> something along the lines of [...]
Nice! I will use that.
Werner
That is because you are using 1 instead of a note name such as c'1. after-
grace does not handle this mechanism.
You can see here that this does work, but it does produce less optimal
spacing:
\relative c' {
<<
\new Staff { \afterGrace f1 { e16[ f] } | g1 }
\new Staff { #(define
Hi Werner,
Alternatively you may try to use \afterGrace to insert the \clef
before the bar line, although this would probably require some
manual spacing too.
This doesn't work at all: `\afterGrace` doesn't accept a clef, as the
image shows.
afterGrace is defined as
#(define-music-function
> [...] I'm rather inclined to count the behaviour of `space-alist`
> for clefs as a buglet: It doesn't make sense allowing the clef to
> move 'under' other notes in different staves while its `space-alist`
> values are applied globally to all staves.
This is now issue #6529.
Hello Valentin,
> My suggestion to getting around this would be the tell Lilypond that
> the clef stencil is in fact narrower than it actually is, which will
> allow the Clef stencil to protrude arbitrarily much: [...]
Thanks! Interestingly, the clef still gets some extra horizontal
space,
Hello Werner,
When doing \afterGrace internally something like
<< [music] { [some-skip] [graces] } >>
is created. These graces will necessarily not fall onto the last timestep of
the measure, which appears to be where the Clef stencil is limited to, which
we can see here:
\relative c' {
<<
Please look at this example.
```
\relative c' {
<<
{ \afterGrace f1 { e16[ f] } | g1 }
{ c1 \clef "bass" | c,1 }
>>
}
\relative c' {
<<
{ f2.. e16[ f] | g1 }
{ c1 \clef "bass" | c,1 }
>>
}
```
What can I do to make the clef move 'under' the grace, similar to the
>> It was diagnosed as a bug in the font (!), not in LilyPond.
>
> Yes, I saw the issue. That's extraordinarily weird.
It's not.
> It is one of the fonts installed with Microsoft Office so maybe this
> should be reported to Microsoft.
Newer versions of this font have it fixed. For example,
gitlab.com/lilypond/lilypond/-/issues/6508
>
>
> It was diagnosed as a bug in the font (!), not in LilyPond.
>
Yes, I saw the issue. That's extraordinarily weird. It is one of the fonts
installed with Microsoft Office so maybe this should be reported to
Microsoft.
Thanks for looking into the
Le 02/01/2023 à 14:31, Jean Abou Samra a écrit :
Le 31/12/2022 à 18:23, Sven Axelsson a écrit :
I sent the font file to you privately.
Thanks, I opened
https://gitlab.com/lilypond/lilypond/-/issues/6508
It was diagnosed as a bug in the font (!), not in LilyPond.
OpenPGP_signature
Le 31/12/2022 à 18:23, Sven Axelsson a écrit :
I sent the font file to you privately.
Thanks, I opened
https://gitlab.com/lilypond/lilypond/-/issues/6508
OpenPGP_signature
Description: OpenPGP digital signature
>
> > > I have just updated my sheet music archive to LilyPond 2.24.0.
> > It went
> > > well, but I am seeing a strange font encoding problem.
> > >
> > > I have installed LilyPond on a Mac M1 running MacOS 13.1 with
> > Ho
ng a strange font encoding problem.
>
> I have installed LilyPond on a Mac M1 running MacOS 13.1 with
Homebrew
> which builds from source using Guile 3.0.
>
> Running this code
>
> \version "2.24.0"
>
> \markup \line { N
On Sat, 31 Dec 2022 at 16:33, Jean Abou Samra wrote:
> Le 31/12/2022 à 14:56, Sven Axelsson a écrit :
> > Hi list,
> >
> > I have just updated my sheet music archive to LilyPond 2.24.0. It went
> > well, but I am seeing a strange font encoding problem.
> >
>
Le 31/12/2022 à 14:56, Sven Axelsson a écrit :
Hi list,
I have just updated my sheet music archive to LilyPond 2.24.0. It went
well, but I am seeing a strange font encoding problem.
I have installed LilyPond on a Mac M1 running MacOS 13.1 with Homebrew
which builds from source using Guile
Hi list,
I have just updated my sheet music archive to LilyPond 2.24.0. It went
well, but I am seeing a strange font encoding problem.
I have installed LilyPond on a Mac M1 running MacOS 13.1 with Homebrew
which builds from source using Guile 3.0.
Running this code
\version "2.24.0"
I’ve opened the issue #1492. This is my first time to open an issue on GitHub.
I’m not so sure I’ve done it correctly.
Best regards,
Jun
> 2022/12/17 22:31、Jean Abou Samra のメール:
>
>
>
>> Le 17 déc. 2022 à 14:28, TamuraJun a écrit :
>>
>> I think it would be nice to document this somewhere
> Le 17 déc. 2022 à 14:28, TamuraJun a écrit :
>
> I think it would be nice to document this somewhere since Frescobaldi is now
> mentioned (and perhaps strongly recommended) in the Learning Manual.
I actually think it should be fixed in Frescobaldi. Can you open an issue on
its bug
Thank you! That worked!
I did not realize that
> “Force use of the tools’ #1 lines” option needs to be checked on
I found that /opt/local/bin/convert-ly (part of 2.22.2) is a python script that
starts with:
#!/opt/local/bin/python3.10
while ~/lilypond-2.24.0/bin/convert-ly is a shell script
> On 17 Dec 2022, at 12:16, TamuraJun wrote:
>
> Hello list,
>
> I’ve been running Lilypond 2.22.2 and Frescobaldi 3.2, both installed with
> MacPorts, on macOS Monterey 12.6.2. I’ve just download “official”
> lilypond-2.24.0-darwin-x86_64.tar.gz, unzip/untar it in my home directory,
> and
1 - 100 of 4273 matches
Mail list logo
