Comment #21 on issue 1663 by philehol...@googlemail.com: Images missing on
web site
http://code.google.com/p/lilypond/issues/detail?id=1663
No. I obviously don't build the lilypond.org website, but my assumption is
that it has to come from /build/out-www/offline-root/Documentation/web/
Comment #22 on issue 1663 by percival.music.ca: Images missing on web site
http://code.google.com/p/lilypond/issues/detail?id=1663
After following the instructions in 6.2, you should have a fully-functional
version of the pages on lilypond.org, with the exception of the old website
in
Comment #23 on issue 1663 by philehol...@googlemail.com: Images missing on
web site
http://code.google.com/p/lilypond/issues/detail?id=1663
The instructions in 6.2 are _much_ more exhaustive than run make
website. If you look at current lilypond.org, everything is there -
pictures, css,
Updates:
Status: Fixed
Labels: Fixed_2_15_8
Comment #6 on issue 1762 by colinpkc...@gmail.com: mutual cues fail
http://code.google.com/p/lilypond/issues/detail?id=1762
(No comment was entered for this change.)
___
bug-lilypond
2011/7/31 Janek Warchoł lemniskata.bernoull...@gmail.com:
Wow, i'm CCed! Why?
You are on my list as aesthetic guru (+ good engraving practices).
And also because Gmail's Consider including feature suggested me to
Cc you (and finally because it usually makes the person reply to the
message,
- Original Message -
From: Xavier Scheuer x.sche...@gmail.com
Since it seems I'm not the only one to consider that Full measure rest
should take more horizontal space (as much horizontal space as a note
of the same duration), could someone open a new issue for this on the
tracker?
Status: Accepted
Owner:
Labels: Type-Defect Priority-Medium
New issue 1798 by philehol...@googlemail.com: Full measure rests do not
occupy correct horizontal space.
http://code.google.com/p/lilypond/issues/detail?id=1798
Music engraving sources suggest that FMRs should occupy the same
Hi,
following the late discussions on bug- and -user, I stumbled over an
ugly collision between a phrasingSlur and a Slur at the beginning of a
second staff. Actually the phrasing slur tries to escape the slur but
does this in a spectacular way - while the collision is still there:
\version
Updates:
Status: Verified
Comment #7 on issue 1563 by philehol...@googlemail.com: strange vertical
line at staff begin using StaffSymbol #'staff-space
http://code.google.com/p/lilypond/issues/detail?id=1563
(No comment was entered for this change.)
Comment #24 on issue 1663 by percival.music.ca: Images missing on web site
http://code.google.com/p/lilypond/issues/detail?id=1663
first: when I follow the link in comment 1, I do not see pictures. I think
that's the final test of whether this is done or not?
second: I took a longer look
Updates:
Status: Fixed
Labels: fixed_2_15_7
Comment #25 on issue 1663 by philehol...@googlemail.com: Images missing on
web site
http://code.google.com/p/lilypond/issues/detail?id=1663
Um. Following a link to a page that shouldn't even be there - one from
2.13 - isn't
Comment #7 on issue 1742 by lemniska...@gmail.com: print transposed guitar
chords on piano sheets
http://code.google.com/p/lilypond/issues/detail?id=1742
I've merged Wol's patches with c++ style formatting changes and ran
regtests again from scratch: everything is still fine.
2011/8/2 Xavier Scheuer x.sche...@gmail.com:
2011/7/31 Janek Warchoł lemniskata.bernoull...@gmail.com:
Wow, i'm CCed! Why?
You are on my list as aesthetic guru (+ good engraving practices).
OMG! That's an honour, thanks!
And also because Gmail's Consider including feature suggested me to
Updates:
Labels: -Patch-new Patch-review
Comment #1 on issue 1796 by pkx1...@gmail.com: LilyPond segfaults on
make-footer = ##f
http://code.google.com/p/lilypond/issues/detail?id=1796
Passes make and reg tests.
___
bug-lilypond mailing
Comment #8 on issue 1775 by pkx1...@gmail.com: doc: add broken- and
unbroken slur shaping function
http://code.google.com/p/lilypond/issues/detail?id=1775
Hello, please find PDF attached of most recent 2.15.9 output - bearing in
mind that the LSR is still at 2.12.x and the ly file contains
Comment #2 on issue 1793 by pkx1...@gmail.com: Doc: change how lyrics in
PianoStaff is documented
http://code.google.com/p/lilypond/issues/detail?id=1793
I looked at the section and while Trevor says to remove the first example,
this would also require a re-write of the para before,
Updates:
Labels: -Patch-review Patch-needs_work
Comment #7 on issue 1779 by lemniska...@gmail.com: accidentaled notes too
far from the barline
http://code.google.com/p/lilypond/issues/detail?id=1779
I see two probably problematic regtests; their output is attached.
note-head-chord -
Comment #3 on issue 1267 by pkx1...@gmail.com: Documentation
for 'ignore-collision is unclear
http://code.google.com/p/lilypond/issues/detail?id=1267
OK we need some clarification here.
The 'reference in the NR' that I can find (but is not really indicated in
the message thread) is in
James Lowe james.l...@datacore.com writes:
From: lilypond-user-bounces+james.lowe=datacore@gnu.org
[lilypond-user-bounces+james.lowe=datacore@gnu.org] on behalf of
Tim Reeves [tim.ree...@tokamerica.com]
Sent: 02 August 2011 19:56
To: lilypond-u...@gnu.org
Subject: Lilypond crashes
On Aug 2, 2011, at 11:15 PM, David Kastrup wrote:
James Lowe james.l...@datacore.com writes:
From: lilypond-user-bounces+james.lowe=datacore@gnu.org
[lilypond-user-bounces+james.lowe=datacore@gnu.org] on behalf of
Tim Reeves [tim.ree...@tokamerica.com]
Sent: 02 August 2011 19:56
Updates:
Labels: -Frog Patch-review
Comment #10 on issue 1776 by pkx1...@gmail.com: Doc: NR - Polymetric
Notation \compoundMeter isn't documented
http://code.google.com/p/lilypond/issues/detail?id=1776
Patch for doc here
http://codereview.appspot.com/4837050
I'd still like the
Status: Accepted
Owner:
Labels: Type-Build Priority-High Patch-new
New issue 1799 by mts...@gmail.com: output-distance.py does not parse
scheme nan values correctly
http://code.google.com/p/lilypond/issues/detail?id=1799
nan values in scheme are issued as +nan.0 and -nan.0, which Python
Status: Accepted
Owner:
Labels: Type-Defect Priority-Critical
New issue 1800 by colinpkc...@gmail.com: Segfault compiling LSR 346
http://code.google.com/p/lilypond/issues/detail?id=1800
User Tim Reeves (tim.ree...@tokamerica.com) reports:
I tried to compile the Creating music with Scheme
On 11-08-02 04:15 PM, David Kastrup wrote:
James Lowejames.l...@datacore.com writes:
From: lilypond-user-bounces+james.lowe=datacore@gnu.org
[lilypond-user-bounces+james.lowe=datacore@gnu.org] on behalf of
Tim Reeves [tim.ree...@tokamerica.com]
Sent: 02 August 2011 19:56
To:
On 11-08-02 10:05 AM, Urs Liska wrote:
Hi,
following the late discussions on bug- and -user, I stumbled over an
ugly collision between a phrasingSlur and a Slur at the beginning of a
second staff. Actually the phrasing slur tries to escape the slur but
does this in a spectacular way - while
Comment #1 on issue 1800 by k-ohara5...@oco.net: Segfault compiling LSR 346
http://code.google.com/p/lilypond/issues/detail?id=1800
% Tinyfying the example leads us to cross staff beams
%
\score {
{ \context Staff = up c8 c %\noBeam % noBeam prevents segfault
\change Staff = down c c
In the following code, no word is placed below the second eight note.
Commenting \cadenzaOn or removing manual beaming [] works fine.
Manual beaming [ ] behaves like slur ( ).
This worked in previous versions.
\version 2.14.0
\score {
\context Voice = notes \relative {
Comment #11 on issue 1776 by lemniska...@gmail.com: Doc: NR - Polymetric
Notation \compoundMeter isn't documented
http://code.google.com/p/lilypond/issues/detail?id=1776
James,
i hoped to answer sooner but i had to fight problems with grand-fixcc.
2011/7/31 Comment #9 on issue 1776 by
Comment #1 on issue 1799 by mts...@gmail.com: output-distance.py does not
parse scheme nan values correctly
http://code.google.com/p/lilypond/issues/detail?id=1799
It seems that my patch fixes the problem - I applied it to the branch where
I'm running my stem regtests, and now the regtests
29 matches
Mail list logo
