> Werner, may I ask you to have a look?
What exactly shall I check?
https://codereview.appspot.com/571640044/
Hello,
Here is the current patch countdown list. The next countdown will be on
February 20th.
A quick synopsis of all patches currently in the review process can be
found here:
http://philholmes.net/lilypond/allura/
***
Push:
5765 Fix portuguese in all copies of utf-8.ly - Han-Wen
Urs Liska writes:
> Am Montag, den 17.02.2020, 13:25 +0100 schrieb David Kastrup:
>> Ok, I think 2.20 is basically done and we should push it out by the
>> end
>> of this week.
>
> This is really great news!
> I'm somewhat undecided whether it is a cause for celebration or not to
> finally rele
Am Montag, den 17.02.2020, 13:25 +0100 schrieb David Kastrup:
> Ok, I think 2.20 is basically done and we should push it out by the
> end
> of this week.
This is really great news!
I'm somewhat undecided whether it is a cause for celebration or not to
finally release a "stable" version after six
>> LilyPond Error
>
> Does it ship with Python, or using the native? The 2.19.83 from the
> site uses 2.6, not 2.7.
> python --version
Python 2.7.17
Werner
On 2020/02/15 21:41:57, thomasmorley651 wrote:
>
https://codereview.appspot.com/571640044/diff/571650043/Documentation/snippets/utf-8.ly
> File Documentation/snippets/utf-8.ly (right):
>
>
https://codereview.appspot.com/571640044/diff/571650043/Documentation/snippets/utf-8.ly#newcode1
> Documentat
Il giorno lun 17 feb 2020 alle 22:35, David Kastrup ha
scritto:
Jean-Charles Malahieude writes:
Le 17/02/2020 à 13:25, David Kastrup a écrit :
Ok, I think 2.20 is basically done and we should push it out by the
end
of this week. This leaves a few days for the translation team to
ca
Jean-Charles Malahieude writes:
> Le 17/02/2020 à 13:25, David Kastrup a écrit :
>> Ok, I think 2.20 is basically done and we should push it out by the
>> end
>> of this week. This leaves a few days for the translation team to catch
>> up with the current state.
>> In particular HINT HINT HINT i
Le 17/02/2020 à 13:25, David Kastrup a écrit :
Ok, I think 2.20 is basically done and we should push it out by the end
of this week. This leaves a few days for the translation team to catch
up with the current state.
In particular HINT HINT HINT it gives the opportunity to native speakers
of l
Reviewers: ,
Description:
Confirm grob-status in input/regression/multi-measure-rest-reminder.ly
Oversight
Please review this at https://codereview.appspot.com/547670044/
Affected files (+2, -0 lines):
M input/regression/multi-measure-rest-reminder.ly
Index: input/regression/multi-measure-r
On 2020/02/17 10:01:29, hanwenn wrote:
>
https://codereview.appspot.com/557380044/diff/569320045/input/regression/multi-measure-rest-reminder.ly
> File input/regression/multi-measure-rest-reminder.ly (right):
>
>
https://codereview.appspot.com/557380044/diff/569320045/input/regression/multi-measur
On 2020/02/17 19:17:04, Dan Eble wrote:
> On 2020/02/17 18:41:58, dak wrote:
> > Are you sure this is actually a working idea? At the beginning of
music,
> Score
> > does not exist and 'Timing is only (reliably?) established as an
alias by the
> > Timing_translator. For polyrhythmic pieces, the T
On 2020/02/17 18:41:58, dak wrote:
> Are you sure this is actually a working idea? At the beginning of
music, Score
> does not exist and 'Timing is only (reliably?) established as an alias
by the
> Timing_translator. For polyrhythmic pieces, the Timing context alias
is moved
> down the hierarchy
https://codereview.appspot.com/557440043/diff/547670043/ly/music-functions-init.ly
File ly/music-functions-init.ly (right):
https://codereview.appspot.com/557440043/diff/547670043/ly/music-functions-init.ly#newcode1319
ly/music-functions-init.ly:1319: 'origin (*location*)
On 2020/02/17 16:59:54,
> On 17 Feb 2020, at 17:04, Werner LEMBERG wrote:
>
>
> For fun I tried to execute
>
>
> https://bintray.com/marnen/lilypond-darwin-64/lilypond-2.19.83/2.19.83.build20200207173449
>
> on my old MacOS Lion box, with the following error.
>
> Traceback (most recent call last):
> …
> ImportE
Reviewers: ,
https://codereview.appspot.com/557440043/diff/547670043/ly/music-functions-init.ly
File ly/music-functions-init.ly (right):
https://codereview.appspot.com/557440043/diff/547670043/ly/music-functions-init.ly#newcode1319
ly/music-functions-init.ly:1319: 'origin (*location*)
I'm curiou
For fun I tried to execute
https://bintray.com/marnen/lilypond-darwin-64/lilypond-2.19.83/2.19.83.build20200207173449
on my old MacOS Lion box, with the following error.
Traceback (most recent call last):
File ".../LilyPond 2.app/Contents/Resources/__boot__.py", line 98, in
_r
Jonas Hahnfeld writes:
> Am Montag, den 17.02.2020, 14:59 +0100 schrieb David Kastrup:
>
>> Yes, GUB for 2.21.0. We don't want to have another indeterminate
>> backlog on unstable releases. That means that GUB needs to get switched
>> over to Python 3.
>
> For those following along: It's not th
Am Montag, den 17.02.2020, 14:59 +0100 schrieb David Kastrup:
> Jonas Hahnfeld <
> hah...@hahnjo.de
> > writes:
>
> > Am Montag, den 17.02.2020, 13:25 +0100 schrieb David Kastrup:
> > > Ok, I think 2.20 is basically done and we should push it out by the end
> > > of this week. This leaves a few d
Jonas Hahnfeld writes:
> Am Montag, den 17.02.2020, 13:25 +0100 schrieb David Kastrup:
>> Ok, I think 2.20 is basically done and we should push it out by the end
>> of this week. This leaves a few days for the translation team to catch
>> up with the current state.
>
> Wohoo!
>
>> [...]
>>
>> W
Am Montag, den 17.02.2020, 13:25 +0100 schrieb David Kastrup:
> Ok, I think 2.20 is basically done and we should push it out by the end
> of this week. This leaves a few days for the translation team to catch
> up with the current state.
Wohoo!
> [...]
>
> What does this mean for 2.21.0? I thi
Ok, I think 2.20 is basically done and we should push it out by the end
of this week. This leaves a few days for the translation team to catch
up with the current state.
In particular HINT HINT HINT it gives the opportunity to native speakers
of languages not as meticulously maintained as the c
On 2020/02/17 10:01:29, hanwenn wrote:
>
https://codereview.appspot.com/557380044/diff/569320045/input/regression/multi-measure-rest-reminder.ly
> File input/regression/multi-measure-rest-reminder.ly (right):
>
>
https://codereview.appspot.com/557380044/diff/569320045/input/regression/multi-measur
https://codereview.appspot.com/557380044/diff/569320045/input/regression/multi-measure-rest-reminder.ly
File input/regression/multi-measure-rest-reminder.ly (right):
https://codereview.appspot.com/557380044/diff/569320045/input/regression/multi-measure-rest-reminder.ly#newcode26
input/regression
On Sat, Feb 15, 2020 at 6:54 PM Torsten Hämmerle
wrote:
> How about consistently introducing languages in their proper spelling (but
> keeping the old names as an alternative?
>
SGTM.
--
Han-Wen Nienhuys - hanw...@gmail.com - http://www.xs4all.nl/~hanwen
On Sun, Feb 16, 2020 at 10:40 PM David Kastrup wrote:
> >> > In this commit, extra support for the case where command-and-args is
> >> empty was added, ie.
> >>
> >> That characterisation is completely wrong. The support is not for the
> >> cases "where command-and-args is empty" but rather wher
On Mon, Feb 17, 2020 at 8:18 AM wrote:
> On 2020/02/16 21:25:42, hanwenn wrote:
> > please, for the love of god, do not use automake.
> >
> > It is slow and arcane, and generally a complete PITA to work with. We
> created
> > stepmake after fighting with automake for a while.
>
> Do you have conc
On 2020/02/17 07:18:25, hahnjo wrote:
> On 2020/02/16 21:25:42, hanwenn wrote:
> > please, for the love of god, do not use automake.
> >
> > It is slow and arcane, and generally a complete PITA to work with.
We created
> > stepmake after fighting with automake for a while.
>
> Do you have concre
28 matches
Mail list logo
