> I'm not top posting.
% Subdivided beams are disregarded with \cueDuring,
% work as expected with \quoteDuring
\version "2.13.48"
music = \relative c'' {
\set subdivideBeams = ##t
\set baseMoment = #(ly:make-moment 1 8)
c16 c c c
}
\addQuote music \music
<<
\new Staff {
\cueDur
Evan Ross gmail.com> writes:
> This is wonderful, thank you for all the help. There's still one more small
> issue -- this appears to change the behavior of slurs, but not of phrasing
> slurs, which remain left-aligned. Is there another property of the Lyric
> context that causes this to happen?
Comment #11 on issue 1211 by joenee...@gmail.com: [PATCH]Optimizations for
pure-height approximations. (issue1817045)
http://code.google.com/p/lilypond/issues/detail?id=1211
Great! So I guess the performance regression in 5266aa is fixed then? All
the files I've run also show some performan
Comment #19 on issue 1105 by pnorcks: clean up our css files
http://code.google.com/p/lilypond/issues/detail?id=1105
And, yes, merging lilypond-website.css with lilypond-manuals.css would be
difficult.
There's only so much we can do when we're using one texi2html init file...
The same HTM
Comment #18 on issue 1105 by pnorcks: clean up our css files
http://code.google.com/p/lilypond/issues/detail?id=1105
IIRC, text-to-speech.css was an experimental CSS file from the web-gop
branch... We can delete this one.
Unless the CSS stylesheets are completely redone, the lilypond-ie-fix
On 2/7/11 12:02 PM, "Tony Hardie-Bick" wrote:
>> I'm not top posting.
>
> % This creates a 10 string tabstaff (for Chapman Stick)
> % in versions up to and including 2.13.45:
>
> \version "2.13.45"
>
> \context TabStaff {
>
> \set TabStaff.stringTunings = #'(-3 -8 -12 -17 -22 -36 -29 -21
Trevor Daniels treda.co.uk> writes:
>
>
>
> No, the positioning is OK, but in a layout block
> you need to omit the "\set".
>
> Alternatively, with "\set", position it at the
> start of the actual lyrics.
>
> Trevor
>
This is wonderful, thank you for all the help. There's still one more sm
On Mon, Feb 07, 2011 at 10:43:27AM -, Trevor Daniels wrote:
>
> Perhaps this should be documented. Apart from noting
> that it must be set in the Lyrics context it seems
> straightforward to use. Does anyone know of any
> difficulty with it?
No, but it wouldn't be hard to ask some users to
Updates:
Status: Accepted
Comment #5 on issue 492 by n.putt...@gmail.com: piano pedal disappears
during RehearsalMark
http://code.google.com/p/lilypond/issues/detail?id=492
(No comment was entered for this change.)
___
bug-lilypond mailing
%% Reported on LilyPond French Users mailing list
%%
http://lilypond-french-users.1298960.n2.nabble.com/Arrangement-vertical-encore-une-petite-amelioration-tp5982503p5998593.html
%%
%% StaffGrouper properties does not apply to "second level" StaffGroup ,
%% i.e. when this StaffGroup is itself
Comment #1 on issue 1506 by n.putt...@gmail.com: \tempo after
StopStaff/StartStaff forces extension of staff symbol
http://code.google.com/p/lilypond/issues/detail?id=1506
I'd suggest setting 'cross-staff as a workaround (rather than
clearing 'X-extent): despite removing the MetronomeMark f
Updates:
Status: Verified
Comment #9 on issue 1463 by colinpkc...@gmail.com: Writing metadata to the
PDF file
http://code.google.com/p/lilypond/issues/detail?id=1463
(No comment was entered for this change.)
___
bug-lilypond mailing list
b
Updates:
Status: Verified
Comment #4 on issue 1257 by colinpkc...@gmail.com: SpanBar at linebreak
disappears when between \stopStaff and \startStaff
http://code.google.com/p/lilypond/issues/detail?id=1257
(No comment was entered for this change.)
Status: Accepted
Owner:
Labels: Type-Defect Priority-High
New issue 1505 by colinpkc...@gmail.com: bendAfter not spanning line break
properly
http://code.google.com/p/lilypond/issues/detail?id=1505
\score {
\new Staff << { s1*3 \break } \relative c' {
s1*2 \times 44/72 {\crescTextCresc
> Comment #8 on issue 1463 by percival.music.ca: Writing metadata to the
> PDF file
>
> This has been raised a few times, and will be discussed in GOP. At the
> moment,
> - undoc'd new features do not block a stable release
> - we can see alterations to regtests with diff, and therefore figur
Comment #17 on issue 1105 by philehol...@googlemail.com: clean up our css
files
http://code.google.com/p/lilypond/issues/detail?id=1105
I've had a quick look at the 2 primary CSS files we now have, and it won't
be possible to blindly merge same or similar styles - there is very little
in
Updates:
Status: Verified
Comment #6 on issue 1035 by colinpkc...@gmail.com: Negative frets in fret
diagrams
http://code.google.com/p/lilypond/issues/detail?id=1035
(No comment was entered for this change.)
___
bug-lilypond mailing list
bu
Comment #10 on issue 1211 by n.putt...@gmail.com: [PATCH]Optimizations for
pure-height approximations. (issue1817045)
http://code.google.com/p/lilypond/issues/detail?id=1211
New timings based on a GUB build of 2.13.48 + patches and standard mingw
binary from lilypond.org:
standard 221m24.
Evan Ross wrote Monday, February 07, 2011 5:04 PM
Keith OHara oco.net> writes:
I hesitate to mention it, but, there is a setting mentioned in
the
Internals
Reference, under Lyric_engraver, that might do what you ask
\set lyricMelismaAlignment = #CENTER
This setting is not in the main doc
Comment #1 on issue 1257 by mts...@gmail.com: SpanBar at linebreak
disappears when between \stopStaff and \startStaff
http://code.google.com/p/lilypond/issues/detail?id=1257
I think this problem has gone away in 2.13.48. Could someone please
confirm?
Attachments:
1257.png 2.3 KB
Graham Percival wrote Monday, February 07, 2011 1:37 PM
On Mon, Feb 07, 2011 at 10:43:27AM -, Trevor Daniels wrote:
Perhaps this should be documented. Apart from noting
that it must be set in the Lyrics context it seems
straightforward to use. Does anyone know of any
difficulty with it
Phil Holmes philholmes.net> writes:
>
> The alignment in that example is incredibly inconsistent - see as an
> alternative measure 6, where Mis is left aligned and face is pretty much
> centred. The alignment on this example is so variable that I suspect
> they've just got it wrong in measure
Keith OHara oco.net> writes:
>
> I hesitate to mention it, but, there is a setting mentioned in the
>Internals
> Reference, under Lyric_engraver, that might do what you ask
> \set lyricMelismaAlignment = #CENTER
>
> This setting is not in the main documentation or the test suite, so it is
>sa
Neil Puttock wrote:
>
> On 1 February 2011 09:15, -Eluze wrote:
>
>> 1) with the code below the accidental is misplaced:
>>
>> \relative c' {
>> \hideCurvesFrom #'Voice.NoteHead #'(0.3 . 0.3) #'(0 . 0)
>> f2 ( gis4)
>> }
>
> I don't think there's any workaround for this short of manually
>
Updates:
Status: Fixed
Labels: Patch-review
Comment #15 on issue 1105 by philehol...@googlemail.com: clean up our css
files
http://code.google.com/p/lilypond/issues/detail?id=1105
Patch emailed to Graham to fix this - we now just have 3 CSS files -
lilypond-manuals.css, lily
On Sun, 2011-02-06 at 14:25 +0100, Reinhold Kainhofer wrote:
> Am Sonntag, 6. Februar 2011, um 06:28:42 schrieb Jay Anderson:
> > An example:
> >
> > \version "2.13.48"
> > \header
> > {
> > title = "Non Lo Farò Più"
> > composer = "Johann Baptist Strauß"
> > }
> >
> > When viewing the pdf th
Updates:
Status: Verified
Comment #6 on issue 1500 by colinpkc...@gmail.com: re-fix note spacing with
melismata
http://code.google.com/p/lilypond/issues/detail?id=1500
(No comment was entered for this change.)
___
bug-lilypond mailing list
On Sun, Feb 06, 2011 at 11:41:13PM +0100, Reinhold Kainhofer wrote:
> > This has been raised a few times, and will be discussed in GOP. At the
> > moment,
> > - undoc'd new features do not block a stable release
> > - we can see alterations to regtests with diff, and therefore figure out
> > w
Comment #1 on issue 1505 by colinpkc...@gmail.com: bendAfter not spanning
line break properly
http://code.google.com/p/lilypond/issues/detail?id=1505
Mike Solomon on lilypond-dev:
While trying to eradicate the bug that's been giving me problems today, I
found this:
http://lilypond.org/do
Updates:
Labels: -Patch-review
Comment #16 on issue 1105 by percival.music.ca: clean up our css files
http://code.google.com/p/lilypond/issues/detail?id=1105
There's no patch to review, because I pushed the patch.
Technically, I'd say that this "topic" isn't finished yet -- it would be
Status: Accepted
Owner:
Labels: Type-Defect Priority-High
New issue 1506 by colinpkc...@gmail.com: \tempo after StopStaff/StartStaff
forces extension of staff symbol
http://code.google.com/p/lilypond/issues/detail?id=1506
From Mike Solomon:
\relative c'' { b1 \stopStaff \override Staff
Reinhold Kainhofer wrote Sunday, February 06, 2011 10:41 PM
Another aspect to consider is that the developer bestk knows what
a new feature is about and how and in which musical context to use
it.
A doc writer, on thze other hand might not have any idea where the
feature can be used (because
Keith OHara wrote Monday, February 07, 2011 7:02 AM
Evan Ross gmail.com> writes:
Is there no way whatsoever to force a center alignment to the
first note of
a multi-note syllable?
I hesitate to mention it, but, there is a setting mentioned in the
Internals
Reference, under Lyric_eng
Status: Accepted
Owner:
Labels: Type-Enhancement
New issue 1503 by colinpkc...@gmail.com: Feature request: simplify jazz
chord display
http://code.google.com/p/lilypond/issues/detail?id=1503
From: Maestraccio
To: bug-lilypond@gnu.org
Subject:Chord name output
Date: Sun,
Updates:
Status: Accepted
Labels: -fixed_2_13_47
Comment #8 on issue 1429 by percival.music.ca: Microsoft Windows version
should not show Ghostscript window
http://code.google.com/p/lilypond/issues/detail?id=1429
accepted.
___
bug-
Status: Accepted
Owner:
Labels: Type-Defect Priority-High
New issue 1504 by colinpkc...@gmail.com: Feathered beams reset at line break
http://code.google.com/p/lilypond/issues/detail?id=1504
The spread of a feathered beam is reset to 0 after a line break. Expected
behavior would be to co
On Sun, 2011-02-06 at 19:34 +, lilyp...@googlecode.com wrote:
> Comment #1 on issue 1257 by mts...@gmail.com: SpanBar at linebreak
> disappears when between \stopStaff and \startStaff
> http://code.google.com/p/lilypond/issues/detail?id=1257
>
> I think this problem has gone away in 2.13.48.
Am Sonntag, 6. Februar 2011, um 23:58:20 schrieb Graham Percival:
> There's five questions in my mind.
>
> 1) should we reject a patch which does not have complete
> documention? (IMNSHO: no)
I would word it differently:
We encourage (although not absolutely require) each developer to write basi
Evan Ross wrote Sunday, February 06, 2011 4:27 PM
I have an idea of what I want to see on the page, found one
instance of that
in this piece, and would like that to be the way my piece is set.
And I find
it difficult to believe given all the individual alterations one
can do in
lilypond tha
On 7 February 2011 10:43, Trevor Daniels wrote:
> Perhaps this should be documented. Apart from noting
> that it must be set in the Lyrics context it seems
> straightforward to use. Does anyone know of any
> difficulty with it?
It doesn't work with manual melismata (using underscores):
\versi
Comment #1 on issue 1504 by colinpkc...@gmail.com: Feathered beams reset at
line break
http://code.google.com/p/lilypond/issues/detail?id=1504
\version "2.13.47"
\header { tagline=##f}
\relative c {
\clef bass
r4.
\override Staff . Beam #'breakable = ##t
<< { \once \override Voice . Beam #'gr
> I'm not top posting.
% This creates a 10 string tabstaff (for Chapman Stick)
% in versions up to and including 2.13.45:
\version "2.13.45"
\context TabStaff {
\set TabStaff.stringTunings = #'(-3 -8 -12 -17 -22 -36 -29 -21 -14 -7)
}
% but this version gives the following error:
% GN
On Sun, 2011-01-30 at 13:13 +, Maestraccio wrote:
> As a jazz musician I read chord symbols from lead sheets all the time.
> Since these must be clear and comprehensive, too much information
> (even though correct) slows down speedy reading and improvising.
> There are some harmonic rules kn
Updates:
Status: Verified
Comment #20 on issue 1268 by brownian.box: [PATCH] span-bar problem
http://code.google.com/p/lilypond/issues/detail?id=1268
I guess it is really fixed -- no tiny example, but regtest added. So,
Verified.
However, that regtest is hard to verify, one will have
Comment #2 on issue 1257 by colinpkc...@gmail.com: SpanBar at linebreak
disappears when between \stopStaff and \startStaff
http://code.google.com/p/lilypond/issues/detail?id=1257
Confirmed in 2.13.49: span bars in both systems.
___
bug-lilypond ma
Evan Ross gmail.com> writes:
>
> Is there no way whatsoever to force a center alignment to the first note of
> a multi-note syllable?
>
I hesitate to mention it, but, there is a setting mentioned in the Internals
Reference, under Lyric_engraver, that might do what you ask
\set lyricMelismaAl
Updates:
Status: Fixed
Labels: fixed_2_13_48
Comment #3 on issue 1257 by pnorcks: SpanBar at linebreak disappears when
between \stopStaff and \startStaff
http://code.google.com/p/lilypond/issues/detail?id=1257
Indeed. The bug exists in 2.13.47 and was fixed in 2.13.48.
>> In searching about the problem people suggest that the text
>> encoding should be utf-16be and include the BOM
Yep.
> It's actually simpler than using utf-16be. All that is needed is to
> use escape sequences instead of the accented characters. E.g. I
> would need to use "\362" instead of "
Trevor Daniels treda.co.uk> writes:
>
> It looks like the engraver intended to follow the standard placement
> for lyrics in most places, but just got it wrong occasionally.
> The most glaring example of this is in page 5, second system,
> last bar. On the alto line both verses have the same wor
>> I suggest to consequently use UTF-16BE (including surrogate
>> support) which can be easily converted from and to UTF-8.
>
> How can I do this in guile?
No idea, sorry. You probably have to write a new routine to do that.
Werner
___
bug-lilyp
Status: Accepted
Owner:
Labels: Type-Defect Priority-High
New issue 1502 by colinpkc...@gmail.com: DOcument information in PDF
headers requires escapes for accented characters
http://code.google.com/p/lilypond/issues/detail?id=1502
An example:
\version "2.13.48"
\header
{
title = "
On Mon, 2011-02-07 at 00:26 +0100, Reinhold Kainhofer wrote:
> Am Sonntag, 6. Februar 2011, um 23:58:20 schrieb Graham Percival:
> > There's five questions in my mind.
> >
> > 1) should we reject a patch which does not have complete
> > documention? (IMNSHO: no)
>
> I would word it differently:
Updates:
Status: Verified
Comment #29 on issue 1472 by colinpkc...@gmail.com: Collision between MMR
and key signature
http://code.google.com/p/lilypond/issues/detail?id=1472
(No comment was entered for this change.)
___
bug-lilypond mailin
- Ursprüngliche Mitteilung -
> > It's actually simpler than using utf-16be. All that is needed is to
> > use escape sequences instead of the accented characters. E.g. I
> > would need to use "\362" instead of "ò".
>
> That's another encoding, PDFDocEncoding (documented in the PDF
> re
54 matches
Mail list logo
