Sad news.
R.I.P Urs
Il mer 1 gen 2025, 10:29 Graham King ha scritto:
> On Tue, 2024-12-31 at 13:40 +0100, Jan-Peter Voigt wrote:
> > Dear Lilypond developers!
> >
> > At the turn of the year I received very sad news. Urs Liska, co-
> > initiator and developer of OpenLilyLib, passed away on Dece
On Sat, Dec 31, 2022 at 1:39 AM Jean Abou Samra wrote:
> Le 31/12/2022 à 01:29, Paolo Prete a écrit :
> > Yeah, I also thought about overlying multiple surfaces.
>
> Nope, no dice.
>
> > But don't exclude my tip: after all, the colors can give you unique
>
Yeah, I also thought about overlying multiple surfaces.
But don't exclude my tip: after all, the colors can give you unique
identifiers for the map I've described to you, and this makes the mechanism
safe
On Sat, Dec 31, 2022 at 1:23 AM Jean Abou Samra wrote:
> Le 31/12/2022 à
e color mechanism is
much safer than you might think.
On Sat, Dec 31, 2022 at 12:41 AM Jean Abou Samra wrote:
> Le 31/12/2022 à 00:29, Paolo Prete a écrit :
> > Hi Jean,
> >
> > Do you have a test snippet for cairo_svg_create_for_stream() ?
> >
> > I would like
Hi Jean,
Do you have a test snippet for cairo_svg_create_for_stream() ?
I would like to make some tests and I googled a bit but could not find
anything useful for it.
Thanks
Il ven 30 dic 2022, 18:17 Jean Abou Samra ha scritto:
> Le 30/12/2022 à 18:12, Paolo Prete a écrit :
> >
On Fri, Dec 30, 2022 at 1:55 PM Jonas Hahnfeld via Discussions on LilyPond
development wrote:
>
> Ok, this is SVG which we can probably agree that the backend is in a
> bad state. At some point, there was a discussion on making Cairo the
> default for producing SVGs but IIRC it faded out with the
On Thu, Dec 29, 2022 at 12:18 AM Jean Abou Samra wrote:
> Le 25/12/2022 à 21:01, Paolo Prete a écrit :
> > Thanks as always for your help, and also for the snippet you provided.
> >
> > You're right it's not usual to do that override twice for the same
>
On Sun, Dec 25, 2022 at 7:02 PM Jean Abou Samra wrote:
> Le 24/12/2022 à 15:38, Paolo Prete a écrit :
> > Hello,
> >
> > I'm noting that the generated SVG of this...:
> >
> > {
> > \once \override DynamicText.output-attributes.val = &qu
Well,
I reordered what I consider erroneous behaviors in the GitLab issue page
On Sun, Dec 25, 2022 at 7:55 PM Jean Abou Samra wrote:
>
>
> Le 25 déc. 2022 à 19:44, Paolo Prete a écrit :
>
>
>
>
> On Sun, Dec 25, 2022 at 7:22 PM Jean Abou Samra
> wrote:
>
>
On Sun, Dec 25, 2022 at 7:22 PM Jean Abou Samra wrote:
>
>
> > Le 25 déc. 2022 à 19:10, Paolo Prete a écrit :
> >
> >
> > BTW:
> >
> > {
> > \override TupletBracket.bracket-visibility = ##f
> > \tuplet 3/2 { s8 s8 s8 }
> &g
ote:
> Le 25/12/2022 à 18:40, Paolo Prete a écrit :
> > What error are you referring to, exactly? In case of my last snippet,
> > which produces a tuplet of three skips, it compiles fine with previous
> > versions.
>
> For me,
>
> \version "2.24.0&q
Thanks, all clear.
On Sun, Dec 25, 2022 at 6:44 PM Jean Abou Samra wrote:
> Le 25/12/2022 à 18:40, Paolo Prete a écrit :
>
On Sun, Dec 25, 2022 at 6:18 PM Jean Abou Samra wrote:
>
>
> > Le 25 déc. 2022 à 18:08, Paolo Prete a écrit :
> >
> >
> > Hello Jean,
> >
> > I just verified that 2.25 doesn't accept a tuplet of skips ( i.e:
> \tuplet 3/2 { s s s }, whil
{
\test { \tuplet 3/2 { e'8 s s } }
}
%---
Thanks very much for your help!
On Sun, Dec 25, 2022 at 1:30 PM Jean Abou Samra wrote:
>
>
> Le 25/12/2022 à 13:27, Jean Abou Samra a écrit :
> > Le 25/12/2022 à 13:02, Paolo Prete a écrit
reakable space character.
> Delete it.
>
> Am Sa., 24. Dez. 2022 um 20:20 Uhr schrieb Paolo Prete <
> paolopr...@gmail.com>:
> >
> > Hello,
> >
> > I just noticed an inconsistent behavior with 2.25.0. The snippet below
> > doesn't compile; I don'
Hello,
I just noticed an inconsistent behavior with 2.25.0. The snippet below
doesn't compile; I don't know if there is a hidden problem inside it, but
it worked for all the versions prior to 2.25:
%---
test = #(define-music-functio
Hello,
I'm noting that the generated SVG of this...:
{
\once \override DynamicText.output-attributes.val = "x"
\once \override DynamicText.output-attributes.val = "y"
c'\mf
}
... creates the following SVG tag, with a duplicate "val" attribute:
Is this a bug? Also note that the dupl
On Wed, Dec 21, 2022 at 10:46 PM Jean Abou Samra wrote:
> Le 21/12/2022 à 22:29, Paolo Prete a écrit :
>
> > 3) I need to test 2.22.0 with GitHub's CI workflow. However, GitHub
> doesn't
> > provide MacPorts for installing software (it only supports Homebrew),
&
Hello,
I'm a bit confused about the available "old" LilyPond versions for Darwin
64.
AFAIK, there are three choices:
A) The unofficial builds on GitLab:
https://gitlab.com/marnen/lilypond-mac-builder/-/releases
B) The MacPorts builds
C) The Homebrew builds
I don't have a macOS, so here are my qu
Il lun 19 dic 2022, 10:41 Jean Abou Samra ha scritto:
> Le 19/12/2022 à 02:46, Paolo Prete a écrit :
> > Hello,
> >
> > Is there a way to install versions up to 2.23.6-1 for Windows without the
> > installer GUI interaction, with a command line that specifies th
I just checked that a possible solution is to unzip the exe archive in
somedir.
Then I called lilypond.exe in usr/bin and it worked fine. However, I wonder
if there can be unwanted side effects in "installing" the program in this
way...
On Mon, Dec 19, 2022 at 2:46 AM Paolo Pr
Hello,
Is there a way to install versions up to 2.23.6-1 for Windows without the
installer GUI interaction, with a command line that specifies the
destination directory?
AFAIK, this is possible for Darwin and Linux, but I can't find a way for
Windows.
On Linux, for example, I do:
echo '\n' | sh
On Sat, Nov 26, 2022 at 11:07 PM Jonas Hahnfeld wrote:
> On Sat, 2022-11-26 at 22:25 +0100, Paolo Prete wrote:
> > Hello,
> >
> > The new releases of LilyPond show how simple it is currently to install
> the
> > program: it is simply a matter of unpackin
Hello,
The new releases of LilyPond show how simple it is currently to install the
program: it is simply a matter of unpacking an archive wherever you want.
This is very powerful and it means that any application (see: editors)
using LilyPond is potentially able to install it automagically, witho
Thank you Dan and Jean.
I'll do some experiments in the next few days and I'll update you.
On Tue, Nov 15, 2022 at 2:39 AM Dan Eble wrote:
> On Nov 14, 2022, at 04:43, Paolo Prete wrote:
> >
> > I need to execute the following automated test:
> > given a .ly fil
Hello,
I need to execute the following automated test:
given a .ly file, I would like to check if the produced output is what I
expect it to be.
Then I was thinking about a way to compare the output (doesn't matter if
PDF or SVG) with an expected image of the same file type, and check if the
two i
On Mon, Oct 17, 2022 at 6:06 PM Paolo Prete wrote:
>
>
> On Sun, Oct 16, 2022 at 1:52 PM Jean Abou Samra
> wrote:
>
>>
>>
>> Thanks for reminding me, this is something that I wanted to
>> share on this list but I forgot. We have a bit of a problem here,
&
On Sun, Oct 16, 2022 at 1:52 PM Jean Abou Samra wrote:
>
>
> Thanks for reminding me, this is something that I wanted to
> share on this list but I forgot. We have a bit of a problem here,
> because Cairo doesn't support setting arbitrary attributes in SVG
> output right now. This corresponds to
Hello,
Is the output-attributes property currently supported on the Cairo backend?
If not, is it planned to be supported?
Thanks!
P
IMHO, you already have an answer and you can already know what is possible
and what will remain possible in the future:
1) If you are planning to *copy* non standard notation (like Stockhausen,
Penderecki etc.) you can simply use LilyPond + Inkscape. Just write a stub
with Lilypond for the standar
ous versions of Lilypond (2.19.84, 2.20.0, 2.22.0, 2.23.0)
Thanks for your feedback!
--
https://github.com/paolo-prete/Spontini
--
%
\version "2.19.84"
\paper {
indent
On Thu, Jul 9, 2020 at 8:35 PM Jean Abou Samra wrote:
> Le 08/07/2020 à 15:31, Paolo Prete a écrit :
>
>
>
> On Wed, Jul 8, 2020 at 12:13 PM Jean Abou Samra
> wrote:
>
>> I would like to emphasize that this is not at all simple. I agree that
>> the technical
On Wed, Jul 8, 2020 at 12:13 PM Jean Abou Samra wrote:
> t to press developers/maintainers to develop anything. My idea was,
> instead, to show how good it could be to use what I consider an
> *impressive* work *already done* by someone else. Just link it, do not
> develop anything.
>
>
> I woul
I have to apologize for the tone I used.
What was wrong was the fact that my words sounded like absolute blaming to
someone/something.
But please, even if I was wrong with this tone (and I can confirm this
again and again): understand that
1) My intention was absolutely not to blame anything of
On Sun, Jul 5, 2020 at 12:14 AM Kieren MacMillan <
kieren_macmil...@sympatico.ca> wrote:
> Hi Paolo,
>
> > What would you consider more readable?
>
> The Feta version.
> The only objection I have is to the kerning in mf — otherwise, I think the
> Feta version is more readable.
>
>
Not so trivial t
>
>
> About this question, I gave an answer to Han-Wen. For example, I consider
> objective data that a fraction where the mumerator is not joined to the
> denominator is more readable.
> Also, look at the attached image in response to Kevin (clefs) with the red
> lines. I consider it objective as
On Sat, Jul 4, 2020 at 10:45 PM Carl Sorensen
wrote:
>
>
> On Sat, Jul 4, 2020 at 2:31 PM Paolo Prete wrote:
>
>>
>> I think there is an incomprehension in the meaning of my words.
>> Unfortunately this does not depend on Lilypond but on commercial logic in
>
27;t give the word "issue" a negative meaning. I think that in this type
of task, "issue" is the most neutral thing in the world. That said, you say
that I should write "in my opinion".
But look at the first six bars of the prelude:
https://github.com/paolo-prete/Sponti
On Sat, Jul 4, 2020 at 4:43 PM Kevin Barry wrote:
> > Again, I hope I am not unpleasant and polemic
>
> In my opinion, you are being both. If your goal was genuinely to
> encourage improvements in LilyPond, then I hope it's clear from the
> response that you are going about it in a poor way. Acti
>
> > This addition does not involve any development. All the stuff is already
> > developed. Just simply, AFAIK, add the fonts to their respective
> > directories, as I have already done.
>
> Here are some things to consider:
>
> * You point to modern printers generating thinner lines. However, th
On Fri, Jul 3, 2020 at 10:19 PM Werner LEMBERG wrote:
>
>
> > I don't understand why this is not part of Lilypond's project. I
> > would use it as default. But, at least, it should be added as a
> > ready-to-use option.
>
> You might not be aware because English is not your mother tongue, but
On Fri, Jul 3, 2020 at 6:05 PM Xavier Scheuer wrote:
> On Fri, 3 Jul 2020 at 16:54, Paolo Prete wrote:
> >
> > They are good, but not GPL/open source...
>
> Hello Paolo,
>
> Most of them were open source initially (Open Font License).
> There are repositories with
ph.
2) it does not bring enough attention of the reader to the glyph
Why are they not already included in Lilypond? It would be really bad to
have troubles with compatibility issues with such a beautiful work...
Best,
P
On Fri, Jul 3, 2020 at 5:17 PM James Lowe wrote:
> On 03/07/2020 13:4
They are good, but not GPL/open source...
On Fri, Jul 3, 2020 at 4:00 PM Andrew Bernard
wrote:
> Nothing at Abraham Lee's satisfies you?
>
> https://www.musictypefoundry.com
>
> Andrew
>
>
> On 3/07/2020 10:48 pm, Paolo Prete wrote:
> > Hello,
>
Hello,
1) Is there a GPL or open-source alternative for FETA fonts for accidentals
that can be used with Lilypond? (If so, is there an example of how to use
them)?
2) IMHO these default accidentals should be changed or improved. The
biggest problem is their vertical lines, which are too bold. As
lphes"):
https://github.com/paolo-prete/Spontini/blob/master/examples/polyphonic-tabular.md
As can be seen, the procedure for obtaining this result consists
1) In the automatically formatted and tabular insertion of cross-staff notes
2) In adding polyphonic voices, using the same cross-staff
On Sat, Jun 27, 2020 at 2:25 AM David Rogers
wrote:
> Paolo Prete writes:
>
> > On Thu, Jun 25, 2020 at 6:00 PM Jean Abou Samra
> >
> > wrote:
> >
> > So, in order to produce a concrete result, at least the
> > point
> >
On Fri, Jun 26, 2020 at 10:35 AM Valentin Villenave
wrote:
> On 6/25/20, Paolo Prete wrote:
> > The lack of a cautionary pedal on a bracket could be seen as an
> enhancement
> > only in a self-referential context, which doesn't make sense to me. A
> > proper wa
On Thu, Jun 25, 2020 at 6:00 PM Jean Abou Samra wrote:
> So, in order to produce a concrete result, at least the point 2) should be
> accepted / understood. This is what I tried to do, but the thread seems to
> go in the opposite way. This is why I think that opening a ticket would be
> unuseful
On Thursday, June 25, 2020, Jean Abou Samra wrote:
> Le 25/06/2020 à 00:58, Paolo Prete a écrit :
>
> Hi Harm,
>
> Then Pierre, who is the creator of the snippet and joined this thread, will
> decide what to do.
>
> Best,
> P
>
> Hi Paolo,
>
> I still h
On Wed, Jun 24, 2020 at 10:53 PM Thomas Morley
wrote:
> Am Di., 23. Juni 2020 um 20:33 Uhr schrieb Paolo Prete <
> paolopr...@gmail.com>:
> >
> > On Tue, Jun 23, 2020 at 6:36 PM Pierre Perol-Schneider
> > A this point:
> >
> > 1) I gently ask Harm (is H
On Tue, Jun 23, 2020 at 10:26 PM Carl Sorensen
wrote:
> On Tue, Jun 23, 2020 at 2:18 PM Paolo Prete wrote:
>
>
> >
> > (Also in response to Carl)
> > In Italy, we call this approach "fare la morale".
> > C's answer made P's words look lik
On Tue, Jun 23, 2020 at 10:32 PM Kieren MacMillan <
kieren_macmil...@sympatico.ca> wrote:
> Hi Paolo,
>
> > I don't understand what you mean exactly, in the choral pieces.
>
> A cappella choral pieces don’t include piano music, and therefore don’t
> include any piano pedal markings, and therefore
On Tue, Jun 23, 2020 at 10:13 PM Kieren MacMillan <
kieren_macmil...@sympatico.ca> wrote:
> Hi Paolo,
>
> > This issue is not *important for me*. It is an *essential* feature for
> any score.
>
> At best, one could argue that it‘s "an essential feature" for any score
> with multiple pedal spanners
On Tue, Jun 23, 2020 at 9:53 PM Jean Abou Samra wrote:
> Paolo,
>
>
> I really think Carl did not intend to be harsh. He even explicitely tried
> to
> avoid making you taking it as an offence:
>
> > I'm trying not to be mean in this answer, but to explain the way
> > LilyPond development works.
>
On Tue, Jun 23, 2020 at 9:32 PM Jean Abou Samra wrote:
> Hi Paolo,
>
> Le 23/06/2020 à 21:09, Carl Sorensen a écrit :
> > Paolo,
> >
> > On Tue, Jun 23, 2020 at 12:33 PM Paolo Prete
> wrote:
> >> 2) Considering that a Pedal cautionary is *essential*
On Tue, Jun 23, 2020 at 9:09 PM Carl Sorensen
wrote:
> Paolo,
>
> On Tue, Jun 23, 2020 at 12:33 PM Paolo Prete wrote:
> >
>
> >
> > 2) Considering that a Pedal cautionary is *essential* in *every* serious
> > score, I really encourage the developers to fix t
On Tue, Jun 23, 2020 at 6:36 PM Pierre Perol-Schneider <
pierre.schneider.pa...@gmail.com> wrote:
> Hi Paolo,
> See: http://lsr.di.unimi.it/LSR/Item?id=1023
> Cheers,
> PIerre
>
>
Hi Pierre,
I already saw your workaround but, as said in the previous email, it has
unwanted side effects.
The first
Paolo Prete
Date: Sat, Jun 20, 2020 at 1:41 AM
Subject: Re: Fine tuning of MetronomeMark's expression
To: Valentin Villenave
Cc: lilypond-user
On Fri, Jun 19, 2020 at 10:44 PM Valentin Villenave
wrote:
> On 6/19/20, Paolo Prete wrote:
> > Is there a way, for the above m
(I re-post this here, because it's a bug and maybe you have an easy fix for
it)
Hello,
please consider this snippet:
%%%
{
\override Staff.TextSpanner.bound-details.left.text = \markup { \small
\bold "Rit." }
\once \override Slur.outside-staff-priority = 100
\once \override DynamicText.outsi
find the code at
> >
> >
> https://github.com/openlilylib/snippets/tree/master/notation-snippets/shaping-bezier-curves/shapeII
> > (don't let the warnings scare you when compiling the example
> file).
> > There would be some figuring out how
Hi Urs,
of course the points you listed must be fixed. I was already aware about
them.
I'm following a specific workflow, and those points will be fixed at a
later time. Meanwhile, it's a good idea to keep track of them.
The workflow is as follows:
1) prepare an * usable *, even if limited, snip
Hello,
the snippet attached to this mail allows the tuning with the mouse of the
curves generated by Lilypond so that the changes can be reflected on the
original .ly file.
The tuning is done on the generated SVG file, as explained in this thread
(but you can look at the code of the attached file,
63 matches
Mail list logo