On Sat, Nov 20, 2010 at 5:10 AM, Alexander Kobel wrote:
> ...or is it known already? I completely lost track of what are different
> bugs and which are not.
> See the attached example; with the increased 'nonstaff-nonstaff-spacing,
> the ChordNames run into the staves they belong to.
> Note that
Comment #7 on issue 1290 by joeneeman: Skyline compaction is going
overboard sometimes
http://code.google.com/p/lilypond/issues/detail?id=1290
System's skyline padding no longer affects vertical spacing because the
systems are not finalized until after vertical spacing (so that we can do
Status: Accepted
Owner:
Labels: Type-Other Priority-Low website
New issue 1420 by v.villenave: Web: add md5sums for binary integrity check.
http://code.google.com/p/lilypond/issues/detail?id=1420
A few French users have requested that we provide md5sums for all the
binary files we offer f
Le 20/11/2010 22:44, Graham Percival disait :
On Sat, Nov 20, 2010 at 9:39 PM, Jean-Charles Malahieude
wrote:
Hoping this is the way you would like me to proceed.
Looks about right, but could we get a proper git commit (i.e. with
your name attached to it, and a commit message) ? I don't wa
Comment #2 on issue 1419 by percival.music.ca: makelsr.py 's convert-ly
should use -d
http://code.google.com/p/lilypond/issues/detail?id=1419
Err, what's "this code" ? If it's something in makelsr.py, then don't
remove it -- it'll be useful after 2.14 is out, and the current D/S/n stuff
On Sat, Nov 20, 2010 at 9:44 PM, Neil Puttock wrote:
> On 20 November 2010 00:22, Graham Percival wrote:
>
>> That *is* the "big picture". If the "time" field is fixed, and
>
> I've just looked at the "time" field issue, and it seems to me it's
> deliberately disabled. The timing info is switch
On Sat, Nov 20, 2010 at 9:39 PM, Jean-Charles Malahieude
wrote:
>
> Hoping this is the way you would like me to proceed.
Looks about right, but could we get a proper git commit (i.e. with
your name attached to it, and a commit message) ? I don't want to
steal credit for this bugfix.
Cheers,
- G
On 20 November 2010 00:22, Graham Percival wrote:
> That *is* the "big picture". If the "time" field is fixed, and
> the "time+cells" are documented, and if the bug squad followed the
> printed checklist in the CG, then we would never need Nick to go
> through and do benchmarks manually. In fac
LGTM
Carl
On 11/20/10 2:39 PM, "Jean-Charles Malahieude" wrote:
> Le 20/11/2010 21:17, Graham Percival disait :
>>
>> On Sat, Nov 20, 2010 at 7:38 PM, Carl Sorensen wrote:
>>> On 11/20/10 12:23 PM, "Jean-Charles Malahieude" wrote:
>>>
instead of the newly formulation
\lang
Le 20/11/2010 21:17, Graham Percival disait :
On Sat, Nov 20, 2010 at 7:38 PM, Carl Sorensen wrote:
On 11/20/10 12:23 PM, "Jean-Charles Malahieude" wrote:
instead of the newly formulation
\language "lingua"
unless there were some Arabic or makam music.xml file around...
The \include "l
On 19 November 2010 23:17, Valentin Villenave wrote:
> That's annoying. Should I reopen #1240? (Or possibly open a new issue
> about it; we should also consider making it a High-prio, since I doubt
> we want to release a new stable version with that much of a
> performance drop.)
As Graham says,
Comment #1 on issue 1419 by n.puttock: makelsr.py 's convert-ly should use
-d
http://code.google.com/p/lilypond/issues/detail?id=1419
everything in Documentation/snippets/new/ should be updated to match the
current git version.
I hadn't noticed this has already happened once before, but i
Status: Accepted
Owner: percival.music.ca
Labels: Type-Other Priority-High Maintainability
New issue 1419 by percival.music.ca: makelsr.py 's convert-ly should use -d
http://code.google.com/p/lilypond/issues/detail?id=1419
the convert-ly call in makelsr.py should use the -d option, to avoid tons
On Sat, Nov 20, 2010 at 7:38 PM, Carl Sorensen wrote:
> On 11/20/10 12:23 PM, "Jean-Charles Malahieude" wrote:
>
>> instead of the newly formulation
>>
>> \language "lingua"
>>
>> unless there were some Arabic or makam music.xml file around...
>
> The \include "lingua.ly" syntax has not been dep
On 11/20/10 12:23 PM, "Jean-Charles Malahieude" wrote:
>
>> It's easy to test if it is currently valid. It's impossible to
>> say if it will ever be deprecated.
>>
>> I suggest you find a musicxml file and try converting it to
>> lilypond a few times, giving different -l values. If you do not
Le 20/11/2010 19:18, Graham Percival disait :
On Sat, Nov 20, 2010 at 11:48:17AM +0100, Jean-Charles Malahieude wrote:
Correcting some typos in the usage manual, I just read in the
section about musicxml2ly:
"@item -l, --language=LANG
use a different language file 'LANG.ly' and corresponding p
On Sat, Nov 20, 2010 at 11:48:17AM +0100, Jean-Charles Malahieude wrote:
> Correcting some typos in the usage manual, I just read in the
> section about musicxml2ly:
>
> "@item -l, --language=LANG
> use a different language file 'LANG.ly' and corresponding pitch names,
> e.g. 'deutsch' for deutsch
Am Samstag, 20. November 2010, um 18:30:56 schrieb Trevor Daniels:
> Nels Daily wrote Saturday, November 20, 2010 5:04 PM
>
> > \version "2.12.3" % necessary for upgrading to future LilyPond
> > versions.
> >
> > % I cannot get the manual beams to extend over all of the rests
> > specified.
> >
Nels Daily wrote Saturday, November 20, 2010 5:04 PM
\version "2.12.3" % necessary for upgrading to future LilyPond
versions.
% I cannot get the manual beams to extend over all of the rests
specified.
\new staff \relative c' {
\time 7/8
r4 e8 r e[ r r] e r r4 e8[ r r]
}
It seems to wo
\version "2.12.3" % necessary for upgrading to future LilyPond versions.
% I cannot get the manual beams to extend over all of the rests specified.
\new staff \relative c' {
\time 7/8
r4 e8 r e[ r r] e r r4 e8[ r r]
}
___
bug-lilypond mailing list
...or is it known already? I completely lost track of what are
different bugs and which are not.
See the attached example; with the increased 'nonstaff-nonstaff-spacing,
the ChordNames run into the staves they belong to.
Note that this is not an artifical example; it's a simplistic, but
common
Hi everybody,
Correcting some typos in the usage manual, I just read in the section
about musicxml2ly:
"@item -l, --language=LANG
use a different language file 'LANG.ly' and corresponding pitch names,
e.g. 'deutsch' for deutsch.ly and German note names."
I wonder if this assertion is still va
22 matches
Mail list logo
