Re: LilyPond 2.24.0 released!
On Thu, Dec 15, 2022 at 1:43 PM Jonas Hahnfeld via LilyPond user discussion wrote: > We are proud to announce the release of GNU LilyPond 2.24.0. > LilyPond 2.24 is brought to you by > > Main Developers: > Jean Abou Samra, Colin Campbell, Dan Eble, Jonas Hahnfeld, Phil Holmes, > David Kastrup, Werner Lemberg, Han-Wen Nienhuys, Francisco Vila > > Core Contributors: > Erlend E. Aasland, Kevin Barry, Martín Rincón Botero, Tim Burgess, > Thibaut Cuvelier, Jefferson Felix, David Stephen Grant, Jordan > Henderson, Masamichi Hosoda, Nihal Jere, Martin Joerg, Michael Käppler, > Doug Kearns, Mark Knoop, Thomas Morley, Lukas-Fabian Moser, Martin > Neubauer, Knut Petersen, Valentin Petzel, Pete Siddall, Alen Šiljak, > Samuel Tam, Timofey, Nathan Whetsell > > Font Contributors: > Johannes Feulner, David Stephen Grant, Owen Lamb > > Documentation Writers: > Michael Käppler, Daniel Tobias Johansen Langhoff, Thomas Morley, John > Wheeler > > Translators: > Federico Bruni, Walter Garcia-Fontes, Dénes Harmath, Masamichi Hosoda, > Guyutongxue, Chengrui Li, Jean-Charles Malahieude, Benkő Pál > > and numerous other contributors. > I'm grateful to all the developers, contributors, writers, and translators. I don't know what I would do without LilyPond! And I'm glad you listed the developers, contributors, writers, and translators. They deserve the recognition! All the best, Ralph __ Ralph Palmer Seattle USA (he, him, his) palmer.r.vio...@gmail.com
Re: Calling in for sickness
On Sun, May 21, 2017 at 5:38 AM, David Kastrup wrote: > Thomas Morley writes: > > > Dear David, > >> Hi folks, > >> > >> had a sort of apoplexy and will not be able to do anything while > >> recovering. I am hospitalized at the moment, CRT and MRT did not show > >> any specific anomalies but my right side is hampered and I cannot yet > >> swallow or cough which is sort of inconvenient. > > Thanks for all your efforts, and for your understanding, for your words > and deeds of support, and for your contributions in making LilyPond > prosper as a great piece of Free Software for articulating beautiful > music. > > -- > David Kastrup Thanks for the message, David. And Thomas Morley, you have my gratitude and best wishes. You will be in my (and many others', I'm sure) thoughts. Ralph -- Ralph Palmer Brattleboro, VT USA palmer.r.vio...@gmail.com ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: Stepping down and moving on
On Wed, Nov 9, 2016 at 12:09 PM, David Kastrup wrote: > > Hi folks and team, > > Partly in connection with a drop of my productivity particularly this > year, the amount of financial support for my work from members of the > LilyPond community went down from overall survivable to disastrous. Of > course this is bitter for those of you that did contribute in > significant amounts to my subsistence but I have to be moving on. David - Words fail me. LilyPond owes you so much. I wish you the best in your new job. Don't be a stranger, Ralph -- Ralph Palmer Brattleboro, VT USA palmer.r.vio...@gmail.com ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: LilyPond 2.18.0 released
On Mon, Dec 30, 2013 at 11:50 AM, David Kastrup wrote: > We are proud to announce the release of GNU LilyPond 2.18.0 - the new > stable release. > Great thanks go to the large number of LilyPond enthusiasts whose > financial backing enabled one core developer, David Kastrup, to focus > exclusively on LilyPond during the entire development cycle. My heartfelt thanks and Happy New Year to all of you involved in LY! Ralph -- Ralph Palmer Brattleboro, VT USA palmer.r.vio...@gmail.com ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Invitation to connect on LinkedIn
LinkedIn I'd like to add you to my professional network on LinkedIn. - Ralph Ralph Palmer Retired at Home Springfield, Massachusetts Area Confirm that you know Ralph Palmer: https://www.linkedin.com/e/n6309e-hjr07if7-4d/isd/15380797458/g-iMAu5u/?hs=false&tok=0qXh86jy4tKBQ1 -- You are receiving Invitation to Connect emails. Click to unsubscribe: http://www.linkedin.com/e/n6309e-hjr07if7-4d/klWuZxyTrQsaD3ax-WBqPxNVgnnZsUem3KY/goo/lilypond-devel%40gnu%2Eorg/20061/I5120571215_1/?hs=false&tok=1Ekbnu170tKBQ1 (c) 2012 LinkedIn Corporation. 2029 Stierlin Ct, Mountain View, CA 94043, USA. ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: Bass figures are not horizontally aligned to whole notes
On Wed, Feb 6, 2013 at 4:13 PM, Marek Klein wrote:
> Hello,
> 2013/2/2 Xavier Scheuer
>
> > My guess is that bass figures should indeed be centered on the note
> > heads (note column), so default behaviour should be changed accordingly.
> > But only the figures. Accidentals, +, etc. should not be taken into
> > account in the "centering", contrary to Bertrand's first "workaround".
> > If someone possessing a reference book could confirm this, thanks.
> >
>
> Could this be considered as the minimal example and the bad output?:
>
>
> \new Staff << { \clef F c1 c c \bar "|."}
>
> \new FiguredBass \figuremode {
>
> <5>1 <6 4+ 2\+> <6>
>
> } >>
>
>
> Marek
Thanks, Marek and Xavier, and my apologies, Marek, for misreading your name
and calling you Mark. This has been submitted as issue 3172 :
http://code.google.com/p/lilypond/issues/detail?id=3172
Ralph
___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: Issue 1798 not verified for whole note full measure rest (4/4 time)
On Tue, Jan 22, 2013 at 6:14 AM, m...@mikesolomon.org wrote: > > > > > Could you let the bug squad know if you need a new tracker for this, > Mike? > > > > Cheers, > > Colin. > > > > Please do, thanks! > > Done. Thanks, Mike. This has been added as Issue 3135 : http://code.google.com/p/lilypond/issues/detail?id=3135 All the best, Ralph ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Bug Squad Rota
Greetings Colin, Bug Squaders, and Developers - Thanks, Colin, for running the scripts and reporting the Bug squad metrics. I have a request to make. I live in the eastern U.S., and at least some of the Bug Squaders appear to live in Europe. My usual (most reliable) time on the computer on the weekend is in the morning. As a result, I frequently don't have any bugs to evaluate when I get up on Saturday morning, and I frequently don't get back to the Bug List until Sunday morning. By that time, someone in Europe has usually snagged my Saturday bugs. In the interest of equity of labor, I'm requesting that someone who has one of the weekdays (where I'm more often at the computer later in the day) switch with me. If no one wishes to switch, I can stay on Saturday, but I probably won't catch as many bugs as I ought. I appreciate your time, your attention, and your help, Ralph ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: No LilyPond Report today
On Sun, Apr 1, 2012 at 5:33 PM, Valentin Villenave wrote: > Hello folks, > you may have noticed that there **isn't** a new LilyPond Report out today. > > Nope. None at all. Sorry. > > And if anything, you will certainly **not** find it here: > > http://news.lilynet.net/?The-LilyPond-Report-25 > > But I didn't tell you that. > > Cheers, > Valentin. Didn't read this until this morning. Almost had me fooled, there, Valentin. I had to cancel my online order of an accordion; made it just in time! Pondly, Ralph -- Ralph Palmer Brattleboro, VT USA palmer.r.vio...@gmail.com ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: @rlsrnamed{Name,Translation} translates also the name in the URI
On Sun, Jan 29, 2012 at 9:38 AM, Federico Bruni wrote:
> Got no answers on -devel, so I forward here (probably more appropriate
> place).
>
> Thanks,
> Federico
>
> Il 05/01/2012 13:44, Federico Bruni ha scritto:
>
>> Issue 1721 reported that @rlsr{Name} keeps the text in english but
>> translates the link in the translated manuals (no idea where the
>> translation comes from).
>> So it recommends to use @rlsrnamed{Name,Translation} instead.
>>
>> But it looks like @rlsrnamed is affected by the same bug.
>>
>> Looking through the log file of make doc I've found a lot of errors like
>> this:
>>
>> WARNING: Unable to find node 'Hauteurs' in book snippets.
>>
>> (look at NR 1.1, you'll find a lot of these broken links)
>>
>> In general, go to the french NR and search for "Morceaux choisis :":
>> you'll see that most of the links are broken.
>>
>> There are some exceptions, for example this works:
>> http://lilypond.org/doc/v2.15/**Documentation/notation/piano.**fr.html
>>
>> (Claviers link down on the page)
>>
>> The syntax used is the same: @rlsrnamed{Name,Translation}.
>> Putting a space after the comma makes any difference.
>>
>> I can't understand the reason of this weird behaviour.
>> Can you please explain what's happening?
>>
>> Thanks,
>> Federico
>>
>
Greetings, Federico and list members -
This has been submitted as issue 2266 :
http://code.google.com/p/lilypond/issues/detail?id=2266
Ralph
___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: a beaming regression?
2012/1/26 Janek Warchoł > Hi, > > i think the output of beam-shortened-lengths.ly doesn't look good, see > in current regtests > http://www.lilypond.org/doc/v2.15/input/regression/collated-files.html > . Am i missing something? > > cheers, > Janek > Thanks, Janek. I agree. It took me awhile to see : it took over 5 minutes to load the page. This has been submitted as issue 2265 : http://code.google.com/p/lilypond/issues/detail?id=2265 Ralph ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: Hairpin #'minimum-length does not apply to real length of the hairpin
On Sun, Jan 8, 2012 at 3:39 PM, Xavier Scheuer wrote:
> Hi,
>
> I noticed this while replying to James.
>
> \override Hairpin #'minimum-length = #8 does not take into account the
> fact that a hairpin can be shortened by the presence of a DynamicText.
>
> "minimum-length" is applied not the real length of the hairpin, but to
> the length of the hairpin **if it would not have been shortened by the
> presence of a dynamic**. IMHO it should apply to the _real length_ of
> the hairpin (the printed one!), even if it is a "shortened hairpin"
> (hey, it is usually these "shortened hairpins" that we —the users— want
> to lengthen when we \override Hairpin #'minimum-length !!).
>
> It is not easy to explain this, I hope the following code will help you
> to understand better what I mean.
>
> Snippet
>
> \version "2.15.24"
>
> \relative c' {
> c1\< |
> c\mf |
> \override Hairpin #'minimum-length = #8
> c\> |
> % this "shortened" (due to the presence of the DynamicText) hairpin
> % does not have a _real_ minimum-length of #8 !
> c1\ppp\<^"too short!" |
> \override Hairpin #'minimum-length = #12
> c\fff\> |
> c\> |
> \revert Hairpin #'minimum-length
> c\mf\> |
> c\p
> }
>
> End of snippet
>
> Cheers,
> Xavier
>
> --
> Xavier Scheuer
Greetings Xavier and list members -
This has been submitted as issue 2207 :
http://code.google.com/p/lilypond/issues/detail?id=2207
I designated it "ugly", but I'm not sure that's the best category.
Ralph
___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: In figured bass, _ direction indicator does not work (^ and - work)
On Wed, Apr 6, 2011 at 9:36 AM, Reinhold Kainhofer wrote: > In figured bass, attaching a text script to a skip (because one has to mark > tasto solo parts with "t.s.") works, but it is not possible to use the _ > direction indicator to print it below the staff. ^ and - work fine. Simple > test case attached. > > The problem happens in 2.12 as well as in 2.13. > > AFAICS, the problem is that in figured bass, _ is redefined in the parser > to > mean an empty figure, so the parser does not detect it as a direction > modifier, even if it is used outside of a bass figure, i.e. not inside > <...>. > > Cheers, > Reinhold > -- > Greetings, Reinhold - This has been added as issue 1594 http://code.google.com/p/lilypond/issues/detail?id=1594 Ralph ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: StaffGrouper properties does not apply to "second level" StaffGroup
On Mon, Feb 7, 2011 at 6:32 AM, Xavier Scheuer wrote:
> %% Reported on LilyPond French Users mailing list
> %%
> http://lilypond-french-users.1298960.n2.nabble.com/Arrangement-vertical-encore-une-petite-amelioration-tp5982503p5998593.html
> %%
> %% StaffGrouper properties does not apply to "second level" StaffGroup ,
> %% i.e. when this StaffGroup is itself contained in an "upper level"
> %% StaffGroup (or equivalent).
> %% Of course the problem is the same for all "Staff-groups"
> %% ( StaffGroup , ChoirStaff , PianoStaff , GrandStaff )
> %%
>
> \version "2.13.48"
>
> \score {
> <<
>\new StaffGroup <<
> \new Staff {
>c'1
> }
> \new StaffGroup \with {
>% this has no effet because
>% this StaffGroup is contained within a StaffGroup (or
> equivalent)
>\override StaffGrouper #'staffgroup-staff-spacing #'basic-distance =
> #20
> } <<
>\new Staff {
> c'1
>}
>\new Staff {
> c'1
>}
> >>
> \new Staff {
>c'1
> }
>>>
> >>
> }
>
>
> Cheers,
> Xavier
>
Thanks, Xavier -
Added as issue 1519 :
http://code.google.com/p/lilypond/issues/detail?id=1519
Ralph
___
lilypond-devel mailing list
lilypond-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: bookTitleMarkup to fill exactly one page (with stretching!) and contain page breaks
Greetings, Reinhold -
On Mon, Nov 22, 2010 at 4:23 PM, Reinhold Kainhofer
wrote:
> For my instrumental scores, I need to create a proper title page using
> bookTitleMarkup. Unfortunately, there are several problems:
>
> -) The lines of the markup are never stretched to be spaced evenly on the
> page
>
> -) If you use hardcoded vertical distances between the lines, the footer
> line
> will be placed either too high or two low, depending on whether some header
> fields use one or two lines
>
> -) There is no page break possible inside the bookTitleMarkup, so you have
> to
> manually add a \pageBreak\allowPageTurn right before the score.
>
> -) The normal title markup can only be generated by abusing the
> scoreTitleMarkup field.
>
>
> Attached is a sample score showing these problems: In one score the
> instrument
> name takes up just one line, in the other score it takes three lines. As a
> consequence, the publisher footer line on the title page is either way too
> much up or way too much down on the page...
>
> Is there any way to create the bookTitleMarkup in a way that
>
> 1) allows page breaks in between (i.e. on the second page there should be
> the
> "normal" title markup
>
> 2) the contents of the title page are stretched, so that one does not have
> to
> use explicit \vspace{..}, which does not work at all.
>
> Thanks,
> Reinhold
>
>
This has been added to the tracker as issue 1443 :
http://code.google.com/p/lilypond/issues/detail?id=1443
Pondly,
Ralph
___
lilypond-devel mailing list
lilypond-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: LyricText #'font-series = #'bold-narrow ?!
On Wed, Oct 20, 2010 at 9:27 AM, Valentin Villenave
wrote:
> Hi Alexander,
>
> CC-ing to the bug list just in case.
>
> On Wed, Oct 20, 2010 at 2:39 PM, Alexander Kobel wrote:
> > why does LyricText #'font-series default to #'bold-narrow?
> >
> > First, it's counterintuitive to me to have a bold narrow font as the most
> > important thing to read in a piece; it's just too black-ish. Condensed
> seems
> > fine for lyrics, but bold?
> > Second, it's defined for nearly no font, in particular Century Schoolbook
> L
> > (the default of LilyPond) does not have it, IIUC, so regular is used
> > instead. At least, this holds for the free typeface; according to
> > Wikipedia, there are Century designs featuring a narrow variant, but
> AFAICS
> > all are commercial, and don't necessarily come as Century /Schoolbooks/.
> > Third, even /if/ it were defined, it doesn't seem to work: I tried
> "Nimbus
> > Sans L", the only font I could find right now which actually offers a
> bold
> > condensed variant (with the same basename, i.e. [1]), and it falls back
> to
> > regular even there. Which came to no surprise after I saw
> >
> > # git grep bold-narrow
> > Documentation/misc/ChangeLog-2.1: * scm/font.scm (paper20-font-vector):
> add
> > bold-narrow series (only
> > Documentation/misc/ChangeLog-2.1: * scm/define-grobs.scm
> > (all-grob-descriptions): use bold-narrow
> > scm/define-grob-properties.scm: include @code{medium}, @code{bold},
> > @code{bold-narrow}, etc.")
> > scm/define-grobs.scm: (font-series . bold-narrow)
> >
> > Is this symbol actually defined somewhere, and what am I missing?
> >
> >
> > [1] This observation makes me wonder: is it possible to define different
> > font basenames for several series of, say, the serif default font? Some
> of
> > my favourite fonts come in two flavours for normal spacing and condensed
> > spacing, and my workaround - if I need both - is to define the condensed
> one
> > as the monospace font to have easy access on it. Which works, but is a
> > complete abuse of the monospace entry. The Real Thing would be to say
> > "GarmdITC Bk BT" is my default serif font, with default proportions,
> > "GarmdITC BkCn BT" is the corresponding condensed font. Some typefaces
> even
> > need the same for bold, ultra-bold or something like this (e.g. Arial vs.
> > Arial Black). And when 'font-series is switched, of course the
> appropriate
> > basename should be chosen.
>
> ___
> bug-lilypond mailing list
> bug-lilyp...@gnu.org
> http://lists.gnu.org/mailman/listinfo/bug-lilypond
>
Greetings -
I'm directing this primarily to bug-list folks. This was submitted over a
week ago, and I see no action. Did I miss something? I don't understand
fonts or typefaces or their parameters well, so I don't understand whether
there is a bug or not. Perhaps this should be a feature request. I'm willing
to add it to the tracker if someone can confirm that it is a bug or else
determine that it should be a feature request. In either case, I'd like
something more succinct.
I appreciate your time and attention,
Ralph
___
lilypond-devel mailing list
lilypond-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-devel
