Hello,
Here is the current patch countdown list. The next countdown will be on
May 22nd.
You can always view the most current countdown list here:
http://code.google.com/p/lilypond/issues/list?q=Patch%3Apush%2Ccountdown%2Creview%2Cnew%2Cwaiting&colspec=Patch%20Owner%20ID%20Summary&sort=patch
___
On 2015/05/17 22:06:10, Trevor Daniels wrote:
> ... I'd prefer
> the syntax and options [of \absolute] to parallel those of
> \relative. That is, an optional prefix pitch to indicate
> the starting octave, and taking the starting octave from
> the first contained note if the prefix is omitted.
Valentin Villenave writes:
> So, my guess would be that we *could* start recommending \language
> "español" rather than \language "espanol" since both syntaxes have
> been available for some time now, and both will still work anyway for
> the time being.
>
> Unless the non-ASCII chars are a probl
On Mon, May 18, 2015 at 9:52 PM, David Kastrup wrote:
> We are recommending "español" over "espanol"? Says who?
Sorry. I should have said: we’re _likely_ to recommend "español" over
"espanol" in the future, now that the syntax allows it. You said
yourself that people had been getting annoyed at
Valentin Villenave writes:
> On Mon, May 18, 2015 at 9:20 PM, Francisco Vila wrote:
>> Besides, this is the status for Spanish users: 'ñ' is a non-shift-needing
>> key in a very prominent place. On the contrary, the very lilypondish '{}[]\'
>> set are all hidden under AltGr.
>
> Likewise here.
>
On Mon, May 18, 2015 at 9:20 PM, Francisco Vila wrote:
> Besides, this is the status for Spanish users: 'ñ' is a non-shift-needing
> key in a very prominent place. On the contrary, the very lilypondish '{}[]\'
> set are all hidden under AltGr.
Likewise here.
> I don't oppose but the alias is che
El 18/05/2015 20:20, escribió:
>
> On 2015/05/18 17:38:22, dak wrote:
>>
>> It does not have non-ASCII notenames, so you might end up with
>
> "español" being
>>
>> the only non-ASCII word in the file
>
>
> How much of a potential problem is it? Even in the absence of non-ASCII
> chars, users are
On 2015/05/18 18:20:20, Valentin Villenave wrote:
On 2015/05/18 17:38:22, dak wrote:
> It does not have non-ASCII notenames, so you might end up with
"español" being
> the only non-ASCII word in the file
How much of a potential problem is it? Even in the absence of
non-ASCII chars,
users a
On 2015/05/18 17:38:22, dak wrote:
It does not have non-ASCII notenames, so you might end up with
"español" being
the only non-ASCII word in the file
How much of a potential problem is it? Even in the absence of non-ASCII
chars, users are already strongly encouraged to use UTF8 encoding in
th
Reviewers: ,
Description:
Rely on the Scheme-computed split state to choose which voice to use
for unisono and unisilence passages.
Please review this at https://codereview.appspot.com/235590044/
Affected files (+4, -62 lines):
M lily/part-combine-iterator.cc
Index: lily/part-combine-iterat
On 2015/05/18 17:08:20, Valentin Villenave wrote:
https://codereview.appspot.com/239930043/diff/1/Documentation/notation/pitches.itely
File Documentation/notation/pitches.itely (right):
https://codereview.appspot.com/239930043/diff/1/Documentation/notation/pitches.itely#newcode492
Documentat
https://codereview.appspot.com/239930043/diff/1/Documentation/notation/pitches.itely
File Documentation/notation/pitches.itely (right):
https://codereview.appspot.com/239930043/diff/1/Documentation/notation/pitches.itely#newcode492
Documentation/notation/pitches.itely:492: @item @code{francais}
Paul Morris writes:
>> On May 18, 2015, at 5:13 AM, Joram wrote:
>>
>> shifting the octave is *not* absolute. So the input
>> \absolute c'' { c' } for c''' is a contradiction in itself.
>> That’s why I strongly recommend not to use \absolute for some kind of
>> non-absolute notation.
>
> +1, an
> On May 18, 2015, at 5:13 AM, Joram wrote:
>
> shifting the octave is *not* absolute. So the input
> \absolute c'' { c' } for c''' is a contradiction in itself.
> That’s why I strongly recommend not to use \absolute for some kind of
> non-absolute notation.
+1, and especially with new users in
On 17/05/15 23:06, tdanielsmu...@googlemail.com wrote:
> On 2015/05/17 21:09:13, dak wrote:
>
>> At any rate, if we were to retain both \fixed and \absolute,
>
> I strongly prefer just two input modes, \relative and \absolute, but
> as I said right at the beginning:
Seonded. With absolute taki
Hi David, hi all,
>> it might not be obvious to strangers to the Helmholtz pitch notation
>> system [1], but shifting the octave is *not* absolute.
>
> LilyPond does not really employ the Helmholtz pitch notation system.
I know. I intended to write that the LP notation is close to the
Helmholtz
https://codereview.appspot.com/239930043/diff/1/Documentation/notation/pitches.itely
File Documentation/notation/pitches.itely (right):
https://codereview.appspot.com/239930043/diff/1/Documentation/notation/pitches.itely#newcode492
Documentation/notation/pitches.itely:492: @item @code{francais}
https://codereview.appspot.com/239930043/diff/1/scm/define-note-names.scm
File scm/define-note-names.scm (right):
https://codereview.appspot.com/239930043/diff/1/scm/define-note-names.scm#newcode566
scm/define-note-names.scm:566: (rébb . ,(ly:make-pitch -1 1
DOUBLE-FLAT))
It would seem to me tha
[1][macupdate-logo.png]
top background
App Listing Updated
Hi lilypond.org, We have updated your application listing for LilyPond
2.19.20-1 on [2]MacUpdate.com. Please take a moment to review your
a
Joram writes:
> Hi,
>
> it might not be obvious to strangers to the Helmholtz pitch notation
> system [1], but shifting the octave is *not* absolute.
LilyPond does not really employ the Helmholtz pitch notation system. We
write c, instead of C and c,, instead of C with a subscripted I and c,,,
Hi,
it might not be obvious to strangers to the Helmholtz pitch notation
system [1], but shifting the octave is *not* absolute. So the input
\absolute c'' { c' } for c''' is a contradiction in itself.
That’s why I strongly recommend not to use \absolute for some kind of
non-absolute notation.
Che
21 matches
Mail list logo
