Status: New
Owner:
Labels: Type-Enhancement Patch
New issue 1095 by neziap: [PATCH] python LilyLib: error and warning as
functions, program_name and _version as variables
http://code.google.com/p/lilypond/issues/detail?id=1095
http://lists.gnu.org/archive/html/lilypond-devel/2010-05/msg0
Status: Accepted
Owner:
Labels: Type-Collision Priority-Low
New issue 1094 by brownian.box: MultiMeasureRest in one voice collides with
noteheads in another
http://code.google.com/p/lilypond/issues/detail?id=1094
Reported by Chris Snyder
(http://lists.gnu.org/archive/html/bug-lilypond/20
On Thu 20 May 2010, 14:41 Chris Snyder wrote:
> Whole-measure rests don't take other voices' notes into
> consideration when deciding on placement, leading to collisions. The
> proper solution, I believe, would be to move the rest as I've done
> manually in the attached use-case.
Thank You, added a
On Mon, 2010-05-17 at 23:58 -0400, Boris Shingarov wrote:
> Hi Joe,
>
> >>> The fact that tight-spacing ignores padding is probably a bug. Do things
> >>> work better if you change minimum_distance to (minimum_distance +
> >>> padding) in page-layout-problem.cc:286?
> >>>
> >> As I had pos
On 05/20/2010 04:08 PM, Xavier Scheuer wrote:
Why did you put the multi-measure rest in \voiceOne and the e'' in
\voiceTwo and not the contrary, which would have been far more logical?
That would be true in the context of this stripped-down test case. In a
larger score, however, this is not al
2010/5/20 Chris Snyder :
> Whole-measure rests don't take other voices' notes into consideration
> when deciding on placement, leading to collisions. The proper
> solution, I believe, would be to move the rest as I've done manually
> in the attached use-case.
Hi!
Why did you put the multi-measu
Whole-measure rests don't take other voices' notes into consideration
when deciding on placement, leading to collisions. The proper solution,
I believe, would be to move the rest as I've done manually in the
attached use-case.
Thanks,
Chris
--
Chris Snyder
Adoro Music Publishing
(616) 828-443
Comment #6 on issue 1036 by paconet.org: Links to accented anchors
http://code.google.com/p/lilypond/issues/detail?id=1036
Now fixed, but we have a side effect on bigpages.
See http://wiki.lilynet.net/index.php/Issue1036 for details.
___
bug-lilypon
Comment #1 on issue 1093 by paconet.org: automatic negative offset for
instrument name positining
http://code.google.com/p/lilypond/issues/detail?id=1093
See also http://code.google.com/p/lilypond/issues/detail?id=771 which is
fixed but
it's the origin of this potential enhancement.
ok, added as
http://code.google.com/p/lilypond/issues/detail?id=1093
Cheers,
- Graham
On Thu, May 20, 2010 at 6:27 PM, Francisco Vila wrote:
>>
> Hello. See #771 http://code.google.com/p/lilypond/issues/detail?id=771
>
> Graham said:
>
>> I'm not certain that I understand the "negative padding
Status: Accepted
Owner:
Labels: Type-Enhancement Priority-Low
New issue 1093 by percival.music.ca: automatic negative offset for
instrument name positining
http://code.google.com/p/lilypond/issues/detail?id=1093
Neil describes the remaining issue clearly. His image
shows what ideally we
>
Hello. See #771 http://code.google.com/p/lilypond/issues/detail?id=771
Graham said:
> I'm not certain that I understand the "negative padding to emulate a vertical
> skyline" issue; if you want this in the tracker, please prepare a tiny
> example for
> the bug-lilypond list, or else just add a
Updates:
Status: Fixed
Owner: ---
Comment #11 on issue 771 by percival.music.ca: Instrument names should be
centered accordingly to StartSystem objects in other staves
http://code.google.com/p/lilypond/issues/detail?id=771
Fixed many weeks before 2.13.21.
Francisco: I don't t
Comment #10 on issue 771 by paconet.org: Instrument names should be
centered accordingly to StartSystem objects in other staves
http://code.google.com/p/lilypond/issues/detail?id=771
I've given 50 USD to the EFF today, via PayPal. Thanks!
How could I show a proof of it?
___
14 matches
Mail list logo
