On 29 June 2010 15:00, Phil Holmes wrote:
> Carrying on looking at documenting undocumented regtests and came across
> chord-scripts.ly. It looks from this as if the regtest is trying to
> demonstrate placement of scripts above and below the chord. Unfortunately,
> this doesn't seem to work. Th
Comment #23 on issue 1031 by n.puttock: constantly-changing
input/regression/rest-collision-beam-note.ly
http://code.google.com/p/lilypond/issues/detail?id=1031
Cheers, Patrick. Yours looks the same as mine. :)
___
bug-lilypond mailing list
bug
Comment #22 on issue 1031 by pnorcks: constantly-changing
input/regression/rest-collision-beam-note.ly
http://code.google.com/p/lilypond/issues/detail?id=1031
I am getting the same results as Neil, running with
$ lilypond lyric-combine-switch-voice.ly
Attached is the backtrace I am seeing
Comment #1 on issue 1157 by n.puttock: Ended Lyrics add extra space between
notes
http://code.google.com/p/lilypond/issues/detail?id=1157
Hmm, I'm leaning towards "Low" here since it's a very subtle difference
(you might class it as a nitpick. ;)
The problem's much easier to see if you re
Comment #21 on issue 1031 by n.puttock: constantly-changing
input/regression/rest-collision-beam-note.ly
http://code.google.com/p/lilypond/issues/detail?id=1031
It happens consistently via the command line or running inside Frescobaldi
(naturally, with --disable-optimising for the binary.)
Comment #20 on issue 1031 by joeneeman: constantly-changing
input/regression/rest-collision-beam-note.ly
http://code.google.com/p/lilypond/issues/detail?id=1031
hm, I can't reproduce it. Do you have a command line that gets the problem
consistently? If not, could you get me a gdb backtrace
Updates:
Status: Fixed
Labels: fixed_2_6_27
Comment #7 on issue 1062 by joeneeman: Pure-height of a system only takes
staves into account, but not other objects
http://code.google.com/p/lilypond/issues/detail?id=1062
(No comment was entered for this change.)
Comment #1 on issue 1159 by n.puttock: Fine-tuning manual beaming
http://code.google.com/p/lilypond/issues/detail?id=1159
This seems to be a conflict between Beam #'beaming and Stem #'beaming,
which is acknowledged in beam.cc:
vector
Beam::get_beam_segments (Grob *me_grob, Grob **common)
{
Comment #19 on issue 1031 by n.puttock: constantly-changing
input/regression/rest-collision-beam-note.ly
http://code.google.com/p/lilypond/issues/detail?id=1031
Joe, have you seen what this does to lyric-combine-switch-voice.ly?
programming error: cyclic dependency: calculation-in-progress e
Updates:
Status: Fixed
Owner: pnorcks
Comment #6 on issue 1160 by pnorcks: css overrides for ie7
http://code.google.com/p/lilypond/issues/detail?id=1160
Everything checks out, and the website looks okay in IE7 now.
___
bug-lilypond ma
Comment #5 on issue 1160 by percival.music.ca: css overrides for ie7
http://code.google.com/p/lilypond/issues/detail?id=1160
ok. Remember that "make website" takes about 1% of the time that "make
doc" does.
oh, but also remember that changes to the website-generation scripts
(including th
Comment #4 on issue 1160 by pnorcks: css overrides for ie7
http://code.google.com/p/lilypond/issues/detail?id=1160
I'm compiling the docs right now with this change, and I'll push if
everything looks okay.
___
bug-lilypond mailing list
bug-lilypon
Comment #3 on issue 1160 by pnorcks: css overrides for ie7
http://code.google.com/p/lilypond/issues/detail?id=1160
Oops, I meant
if (not ($web_manual)) {
}
___
bug-lilypond mailing list
bug-lilypond@gnu.org
http://lists.gnu.org/mailman/listinfo/
Comment #2 on issue 1160 by pnorcks: css overrides for ie7
http://code.google.com/p/lilypond/issues/detail?id=1160
Aha! It would have helped if I checked the source code first (from the
texi2html init file):
# FIXME: the website doesn't use ie7-specific fixes; do the
# docs still need t
Comment #5 on issue 1043 by k-ohara5...@oco.net: beams no longer count
towards boundary boxes
http://code.google.com/p/lilypond/issues/detail?id=1043
The issue occurs in stable 2.12.3 as well. Short example input attached.
Produced by staff-crossing either a) within or adjacent to an automa
Comment #1 on issue 1160 by pnorcks: css overrides for ie7
http://code.google.com/p/lilypond/issues/detail?id=1160
Hmm, last time I checked, IE7 didn't *need* any special CSS overrides for
the new website.
I'm looking into it...
___
bug-lilypond
Not sure if that's what you meant. Currently we have:
< c_^ e^^ > 4
< c_^ e^^ > 4
Think we should have:
< c_^ e^^ > 4
< c_^ e_^ > 4
No ^_
--
Phil Holmes
Bug Squad
"Graham Percival" wrote in message
news:aanlktinq-pkom9qq7x_9jss49ynsj3-flv5erw6bk...@mail.gmail.com...
The regtest has
This might be due to the setting of Compatibility View in IE.
Activating this in IE8 causes the same incorrect display to appear.
Trevor
___
bug-lilypond mailing list
bug-lilypond@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-lilypond
The regtest has been changed to test ^ _ and _ ^ . No code has been
changed; if .27 looks bad (well, if there's a mismatch between text
and graphics), then please add an issue.
Cheers,
- Graham
On Tue, Jun 29, 2010 at 5:10 PM, Phil Holmes wrote:
> The regtest or the behaviour?
>
> --
> Phil
The regtest or the behaviour?
--
Phil Holmes
Bug Squad
"Graham Percival" wrote in message
news:aanlktille0qaueyptotjntsw2mlj2fluruq4ns3yq...@mail.gmail.com...
Thanks, changed in git. It should look different in 2.13.27.
Cheers,
- Graham
On Tue, Jun 29, 2010 at 3:00 PM, Phil Holmes wrote
Thanks, changed in git. It should look different in 2.13.27.
Cheers,
- Graham
On Tue, Jun 29, 2010 at 3:00 PM, Phil Holmes wrote:
> Carrying on looking at documenting undocumented regtests and came across
> chord-scripts.ly. It looks from this as if the regtest is trying to
> demonstrate plac
Status: Accepted
Owner:
Labels: Type-Documentation Priority-Critical website
New issue 1160 by percival.music.ca: css overrides for ie7
http://code.google.com/p/lilypond/issues/detail?id=1160
IE 7 apparently needs some special CSS handling. I remember seeing
something about that in old d
Status: Accepted
Owner:
Labels: Type-Defect Priority-Postponed
New issue 1159 by PhilEHolmes: Fine-tuning manual beaming
http://code.google.com/p/lilypond/issues/detail?id=1159
In the snippet below, the override seems to shift the baseline for beaming
in an undesirable way. This does not
"Carl Sorensen" wrote in message
news:c84f5ada.13762%c_soren...@byu.edu...
On 6/28/10 10:36 AM, "Phil Holmes" wrote:
> I _think_ I've found a bug in manual beaming. See the snippet below and
> the
> image. In the last example in the snippet, the beams end up higher than
> they should be
On 6/28/10 10:36 AM, "Phil Holmes" wrote:
> I _think_ I've found a bug in manual beaming. See the snippet below and the
> image. In the last example in the snippet, the beams end up higher than
> they should be. This seems to be a consequence of having more than one note
> between the overr
Carrying on looking at documenting undocumented regtests and came across
chord-scripts.ly. It looks from this as if the regtest is trying to
demonstrate placement of scripts above and below the chord. Unfortunately,
this doesn't seem to work. There's also what seems to be a bug in the
regtes
Comment #2 on issue 1038 by percival.music.ca: more technical website items
http://code.google.com/p/lilypond/issues/detail?id=1038
any goals for the google analytics part of the website must be in
script/build/website_post.py
to avoid screwing up non-website builds.
Hi Richard,
I believe this is another manifestation of the bad patch for 1062 which
Joe reverted a few days ago. The fix is in Git.
Boris
On 06/29/2010 03:41 AM, Richard Sabey wrote:
I am not top-posting.
% If the music has at least one tall system and many vertically-short systems,
Status: New
Owner:
Labels: Type-Documentation Patch
New issue 1158 by neziap: [Doc Patch] Re: (2.13.x) bottom-system-spacing
http://code.google.com/p/lilypond/issues/detail?id=1158
http://lists.gnu.org/archive/html/lilypond-devel/2010-06/msg00396.html
_
> I am not top-posting.
% If the music has at least one tall system and many vertically-short systems,
% v.2.13.26 gives the vertically-short systems too much vertical space.
% When using Feta font size 20 and A4 paper, Lilypond v.2.13.26 lays this
% example out on 4 pages, 4 systems per page. Thi
30 matches
Mail list logo
