s_broken ())" branch is
quite different from the code in the actually taken branch. So I am
somewhat hesitant in throwing out the code that (right now) is never
reached.
Mike? Any idea what was the intent here and what the correct way to
make it happen
translation branch?
I think it is awfully outdated and half-German (and the German parts are
copies from awfully outdated source as well). We really need more
active translators, and this translation wasn't even finished.
--
David Kastrup
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
up a SF account and post the user name to the Dev list.
>
> And, Mike, we never push to Master - always to Staging, even after testing.
>
> Trevor
It seems like a pain to create an account just for that even though it
might come handy afterwards. I expect
he English documentation, we should likely
do that.
Maybe we should offer an additional link to the English versions for
_all_ languages knowing to have an outdated translation, including
German and Dutch.
--
David Kastrup
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
mi -- lis il -- li __ non in
> }
>
>
> \score {
> <<
> \new StaffGroup
> <<
>\new Staff { \tenor }
>\addlyrics { \tenor_lyrics }
>\new Staff { \bass }
>\addlyrics { \bass_lyrics }
> >>
> >>
m before :) )
>
> The first example has an extender only because the default minimum
> length is 1.5. if that is reduced to 0 that extender vanishes altogether
> in 2.19.55.
This is a consequence of
commit 6c6d1f6ac9e6a7a9aba760dcbb41b4fbbc8f0536
Author: David Kastrup
Date: Sat Feb 4 14
\new Staff \relative { c''4 \bar ".|:" \grace s16 d2. }
>>
Please make sure that you use the ‘\grace’ command for the spacer
part, even if the visual part uses ‘\acciaccatura’ or ‘\appoggiatura’
because otherwise an ugly slur fragment will be printed, connecting the
invisible grace note with the following note.
--
David Kastrup
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
> undesired) behaviour. Not sure whether it's fixable in the
> afterGrace-definition.
Easy enough: wrap a (descend-to-context ... 'Bottom) around its
definition. However, this breaks \displayLilyMusic in bewildering ways.
Still trying to figure out what's happening there.
--
David Kastrup
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
Thomas Morley writes:
> 2017-02-22 23:08 GMT+01:00 David Kastrup :
>
>> Easy enough: wrap a (descend-to-context ... 'Bottom) around its
>> definition. However, this breaks \displayLilyMusic in bewildering ways.
>
>
> Doing so, i.e.:
>
> afterGrace =
&g
David Kastrup writes:
> Easy enough: wrap a (descend-to-context ... 'Bottom) around its
> definition. However, this breaks \displayLilyMusic in bewildering ways.
>
> Still trying to figure out what's happening there.
Here is the minimal breaking example (should break
David Kastrup writes:
> Thomas Morley writes:
>
>> 2017-02-22 18:44 GMT+01:00 Klaus Rettinghaus
>> :
>>> Hi there,
>>>
>>> when the music starts with an \afterGrace the layout is broken:
>>>
>>> \relative { \time 2/4 \afterGrace g
ranslations
up-to-date. Currently there is no German translator active.
I fixed the other typos without raising a separate issue for it.
--
David Kastrup
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
e honest, it feels a bit
futile to fix the typos in documentation that is rather outdated. Could
you be interested in working on updating the German translation as well?
There hasn't been serious translation work for years now.
--
David Kastrup
___
ued elsewhere
in the same time step.
The important thing is "in the same time step": if one of your continued
implicit voices starts with a grace, you need manual grace note
synchronization in order not to have other implicit voices rip off from
their continuation.
So it's fragile.
reRestNumber for reaching it now.
For now, use
\tweak MultiMeasureRest.output-attributes.id #'multi-measure-rest
R1*8
--
David Kastrup
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
ernatively, wait for 2.19.58 where the default has been changed
accordingly. Fixing this properly would require analyzing what the
dorito extendersOverRests actually does and what it should be doing
instead.
--
David Kastrup
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
oken and/or tried
the second form?
--
David Kastrup
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
command that looks like an override must be hardwired into the parser.
I am not really all too eager to try smuggling setter functions
returning a music expression into the parser, so this is likely to stay
in that manner. It would seem more sensible to change overrides to have
tweak s
some rational or floating-point number.
If LilyPond "should surely provide", the question is _what_ should it
provide? I don't see that there is a ready answer for that.
--
David Kastrup
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
Simon Albrecht writes:
> Am 28.03.2017 um 17:47 schrieb David Kastrup:
>> Urs Liska writes:
>>
>>> As discussion onhttps://github.com/wbsoft/python-ly/pull/90 shows
>>> floating point metronome numbers are surely something LilyPond should
>>> pro
Urs Liska writes:
> Am 28. März 2017 18:41:55 MESZ schrieb David Kastrup :
>>This is not how (binary) floating point works.
>>
>>100.1 may well be 100.09997 or similar. There is absolutely no
>>issue with letting LilyPond _accept_ non-integers. But I don
t; \tempo 2 = #'(8683/1000 . "86.83")
Well, there _is_ #e86.83 to save you from getting your fraction wrong by
an order of magnitude...
So we have a technically feasible proposal on the table. But, well,
ugh? I think we are better off with some solution with fixed formatting
(say, ~
ingle-Staff Staffgroup.
>
> ChoirStaff works great though.
> Playing with X-offset and extra-offset (which ignores the *invisible wall*)
> can be a quite correct workaround.
Pretty sure this is
commit 9edf3715c2b2cca09785dcd015724ad3c29cba8a
Author: David Kastrup
Date: Thu Dec 26 16:07:5
Dan Eble writes:
> David wrote:
>> It would seem more sensible to change overrides to have
>> tweak syntax and forego the gratuitous equals sign.
> That would be an improvement.
It would be sort of a drastic change.
--
David Kastrup
_
he --pdf option, so I'm wondering if there is a way
> to fix this bug?
Those look like hyperlinks, even though they are at useless places. You
don't want to link to the source anyway, so try passing the
-dno-point-and-click
option to LilyPond (don't actually know how this
without
change. LilyPond-book calls several other programs but LilyPond would
seem to me the most likely one to augment with user-specified options.
That does not help your problem: it was just a musing.
Does this happen with the "book" document class as well or is this
specific to scrbook?
--
David Kastrup
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
ether the current context type
would be accepted by the parent directly. But I'm not sure we should
rely on such knowledge as a user interface: there might be good reasons
for moving additional (mostly implicit) layers into the context
hierarchy without having to change the bulk of the
David Kastrup writes:
> Dan Eble writes:
>
>> %{
>> NullVoice is unlike a Voice in this respect: trying to move it to a
>> different Staff with \change fails with this warning:
>>
>> Change_iterator::process (): NullVoice = `soprano':
>>
ch more of a headache than most code changes since there is no
"obviously best" regtest to aim for.
Thanks
--
David Kastrup
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
x27;s likely a pretty direct way to figure out where the
NullVoice went. One doesn't get to see a lot of it otherwise.
I guess I'll take it. Thanks.
--
David Kastrup
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
re is issue 4068 doing
such a rule, but also reverting it again. Presumably I did not think
the rule robust enough to be enabled permanently. But obviously this is
a problem we should not just ignore. Perhaps do a version that will
work after a line beginning and/or { ?
--
David Kastrup
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
David Kastrup writes:
> Noeck writes:
>
>> perhaps I am too demanding, but shouldn't this syntax be updated by
>> convert-ly?
>>
>>
>> \version "2.16.0"
>>
>> \paper {
>> system-system-spacing #'padding =
David Kastrup writes:
> David Kastrup writes:
>
>> Noeck writes:
>>
>>> perhaps I am too demanding, but shouldn't this syntax be updated by
>>> convert-ly?
>>>
>>>
>>> \version "2.16.0"
>>>
>>> \p
om different LilyPond versions)?
My guess would rather be on some auto-encoding/decoding choice by
Python, possibly triggered by badly (or unexpectedly?) encoded material
in the MusicXML file.
--
David Kastrup
___
bug-lilypond mailing list
bug-lilypon
ehead it is attached to?
A stem could be attached to several different noteheads ("string
chords", usually arpeggiated in some manner). LilyPond does not do this
well currently but that does not mean that it shouldn't: it is a common
type of no
Knut Petersen writes:
> Am 05.07.2017 um 10:26 schrieb David Kastrup:
>> Knut Petersen writes:
>>
>>> Shouldn't a stem not have a duration equal to the duration of the
>>> notehead it is attached to?
>> A stem could be attached to several diff
are actual
spaces like
"Et in nomine tuum aeternum"
Not when you have a lot of different syllables not containing any space
internally.
So it more or less applies to "drone notes" which are filled with
multiple syllables.
--
David Kastrup
ot;.
So you'd see it used when writing stuff like (implicit \line):
\version "2.19.64"
\score {
<<
\relative { g'1 }
\addlyrics {
\override LyricText.word-space = #9
\markup { Requiem aeternam dona eis, Domine }
}
>
uring make
> doc with lilypond segfaulting:
[...]
> Any idea?
Same as with Fedora et al.
Cherry-pick
commit 93f3d637efbc038b837cf64fae0872e873e4f039
Author: David Kastrup
Date: Fri Sep 2 23:11:53 2016 +0200
Issue 4965: Create and use Grob::parent_relative
This function ch
ing: never use \stemDown rather than \voiceTwo unless you
know _exactly_ what you are doing and will feel responsible for dealing
with every consequence.
--
David Kastrup
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
>> Expected result: all music and lyrics are red
>> Observed result as of 2.19.57: All music and lyrics except for the
>> LyricHyphen are red
>>
>> kind regards,
>> Hans Aikema
>>
> Sorry, forgot to check open issues…. already registerd as bug# 5110
;
> }
They aren't "conflicting". Each block causes one output to be generated
under possibly different conditions (and possibly setting different file
names), just like each \midi block causes a Midi file to be generated.
--
David Kastrup
__
> (which is what? 3 years old now).
>
>
> This happens with 2.19.57 too.
Touching the font cache when converting the documentation with
Ghostscript from PS to PDF might just be a side effect of running the
system's Ghostscript. In that case, it would be more a probl
Yuri writes:
> On 08/17/17 09:23, David Kastrup wrote:
>> Touching the font cache when converting the documentation with
>> Ghostscript from PS to PDF might just be a side effect of running the
>> system's Ghostscript. In that case, it would be more a problem
don't rely on an implicitly
created Staff. But why use \context instead of \new ?
This resembles a bit a collection of worst or at least weird practices
and I wonder just _where_ you even learnt about them. I am pretty sure
(or at least hopeful) that LilyPond's documentation would
"Trevor Daniels" writes:
> David Kastrup wrote Friday, August 18, 2017 3:00 PM
>
>
>> bb writes:
>>
>>> With
>>> indent = 0\mm
>>> activated the first bar will be wrong, as the first notes of voice one
>>> and two align. They
text Lyrics \lyricsto "V" { Ah __ _ __ \skip 1 buh. }
>>
where no extender at all gets printed.
The takeaway for this is that extenders at the current point of time
often don't work as expected and are pretty hard to make do something
useful. I have a hard
xtender syntax, then
tries to do the right thing by itself.
Interpreting user input sensibly and ignoring user input altogether are
not the same thing.
--
David Kastrup
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
Thomas Morley writes:
> 2017-08-26 20:13 GMT+02:00 David Kastrup :
>> Dan Eble writes:
>>
>>> %% Semantically, the melisma ends at the skip.
>>> %% In the output, the extender continues to the next syllable.
> [...]
>> I've had other occasion
mail programs automatically set the correct internal headers when
> simply replying to e-mail – only this is one of the best reasons for
> turning digest mode off.
Could be an argument for making
ruf = \repeat unfold \etc
work. At the current point of time, \repeat is built-in, and that
into committable state than it
turned out I was able to muster.
Yes, this is still unfinished business and no, my own involvement with
it being unfinished is less than fabulous.
But harping won't get the work done.
--
David Kastrup
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
set in main input).
--
David Kastrup
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
}
> \new Lyrics \lyricsto "3" { Cc Dd }
> }
>>>
>
> <<
> \context Voice = "4" \music
> {
> \new Lyrics \lyricsto "4" { Aa Bb }
> \new Lyrics \lyricsto "4" { Cc Dd }
> }
>>>
What are you trying to do?
ricsto-controlled contexts in sequence particularly don't
make a lot of sense. Different Lyrics contexts in sequence don't make a
lot of sense in the same manner as different Staff contexts in sequence
don't make a lot of sense: they will start a new "line". There may be
situations in connection with repeats where there is a point.
--
David Kastrup
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
tually more of a
head-scratcher.
--
David Kastrup
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
James writes:
> On Mon, 04 Sep 2017 08:38:02 +0200
> David Kastrup wrote:
>
>> Dan Eble writes:
>>
>> > So difficult to do anything about that it’s not worth tracking.
>> > Very well.
>>
>> I don't know whether we have an issue ent
Staff = "upper" \upper
> \new Staff = "lower" \lower
> >>
> \layout { }
> \midi { }
> }
> <http://lilypond.1069038.n5.nabble.com/file/t5399/IMG_1025.png>
I don't see a bug. You force a break before and after the grace note.
So t
ue of current master ... has anybody investigated
> the problem ?
I don't know whether we have an issue in the tracker for this, but it
will always be an issue since there is no valid output for this input
(I don't think one can have both a flag and a stem trem
Knut Petersen writes:
> Am 15.09.2017 um 23:20 schrieb David Kastrup:
>>
>>>>> \version "2.19.39"
>>>>>
>>>>> \relative c' {
>>>>> c8:32 c32 c c c
>>>>> }
>>>>>
>&g
t; \storePredefinedDiagram #default-fret-table \cmSevenA % cd#ga#
> #Cuatro
> #"1-1; 1-1;o;o;2-2;"
> \new FretBoards {
> \set Staff.stringTunings = #Cuatro
> { \cmSevenA \break \bar "||" }
a broken staging, either by checking yourself or creating an
issue after all).
We have had a fair share of "this could not possibly break compilation"
kind of changes breaking compilation.
Also any possibility for contention is worth a review. This here seems
solid enough to me.
--
David
marked
\staccato. The default value for ac:portatoFactor is 3/4 (to match the
current default shortening factor for notes marked \portato when not using
articulate.ly).
Don't see an obvious candidate for the problem immediately.
--
David Kastrup
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
n the 'articulations of a note-event and
> in the elements of an event-chord? See:
> { \displayMusic -2 }
articulate is from before Issue 2240 time and is written that way. It
has been "adapted" by calling event-chord-wrap! and thus does its job
using pre-2240 expression hand
; \new Staff { c''1*2 \glissando c'' }
> \new Staff { c''1*4 \glissando c'' }
> \new Staff { c''1*8 \glissando c'' }
> \new Staff { c''\breve \glissando c'' }
> % work
Thomas Morley writes:
> 2017-10-03 13:14 GMT+02:00 David Kastrup :
>> Thomas Morley writes:
>>
>>> Hi all,
>>>
>>> in Staff-context glissando is wrongly positioned if between notes with
>>> duration \longa
>>>
>>> \version
, improves longas (Issue 3480)
>
> Those patches tackle the skyline-problem, which causes the cut off previews.
> So it's no good option to revert them.
>
> Maybe glissando should look at staff-position?
That sounds sensible.
--
David Kastrup
_
Thomas Morley writes:
> 2017-10-03 18:18 GMT+02:00 David Kastrup :
>> Thomas Morley writes:
>>
>>> Version: 2.16.2: longa-note-head-stencil Y-extent: (-0.550006 . 0.550006)
>>> Version: 2.19.65: longa-note-head-stencil Y-extent: (-0.72 . 3.519982)
>&
iate a separate "output" type like a context definition is
instantiated into a context. Instead, output definitions may receive
the side effects from their uses (which include managing the writing of
a Midi/PDF file, and in this case, causing font definitions).
--
David Kastrup
Thomas Morley writes:
> 2017-10-08 13:36 GMT+02:00 David Kastrup :
>>
>> I think using a different layout than the one your output appears in
>> is not a supported idea. Output definitions are hemimetabolic. They
>> may be an "output definition" but it
anything else in 2.12.0.
I don't see that we can do this significantly better than it is
currently done.
--
David Kastrup
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
altogether? I do try to keep rules "idempotent" as much as possible,
making it harmless to apply them multiple times in a row. That allows
just trying another sweeping convert-ly run. But this isn't really
possible for all rules.
--
David Kastrup
__
Alex Schreiber writes:
> On 2017-11-01 10:51, David Kastrup wrote:
>>
>> I don't really agree: that way lies madness. Do we take the time when
>> something stops working reliably, or the time when it stops working
>> altogether? I do try to keep rules
ty coding.
Assertion failures should not be triggered by users anyway. They point
to a violation of the program's assumptions severe enough that it makes
no sense to continue. So this should likely become a programming error
instead.
You still won't get sensible behavior here since the retu
Thomas Morley writes:
> 2017-11-08 23:40 GMT+01:00 David Kastrup :
>> Thomas Morley writes:
>>>
>>> {
>>> \override Fingering #'stencil =
>>> #(lambda (grob)
>>> (ly:grob-set-property! grob 'stencil
>>>
Thomas Morley writes:
> 2017-11-08 23:56 GMT+01:00 David Kastrup :
>> Thomas Morley writes:
>>
>>> 2017-11-08 23:40 GMT+01:00 David Kastrup :
>>>> Thomas Morley writes:
>>>>>
>>>>> {
>>>>> \override Finger
ally well with tuplets, and particularly it does not
answer the question of how to do subdivisions if they are present as
well.
--
David Kastrup
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
\version "2.19.80"
>
> melodyone = \relative { \time 4/4 \key c \major c1}
> \book { \bookOutputName "melody1" \bookpart { \score { << \new Staff
> {\transpose c c \melodyone } >> } } }
That is not a lilypond-book source file. Can you come up with an
Part of the problem is that lualatex keeps all pdf files that are include via
> \includegraphics open, so reaching 1023 open files is possible.
> xelatex behaves differently - it does not keep files included by
> \includegraphics open.
That sounds like something that would be worth repor
-doc".
I thought our default idea was to use xelatex?
--
David Kastrup
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
/>
is tagged Fixed_2_19_25 so you should not see this problem with current
developer/prerelease versions.
--
David Kastrup
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
rge.net/p/testlilyissues/issues/5260/)
Rietveld issue: 339220043 (https://codereview.appspot.com/339220043)
Issue description:
Let Key_performer heed instrumentTransposition I actually have no
good idea how to regtest this one.
--
David Kastrup
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
Staff \mus
\new TabStaff \tab
>>
}
The point of a ChoirStaff is, uh, to have bars not going through
vertically but still get a bracket.
Well, uhm. Sounds like accepting TabStaff by default might be sensible
to do?
At any rate, what happens here is that the ChoirStaff creates a
Staff
Simon Albrecht writes:
> On 22.01.2018 18:29, David Kastrup wrote:
>> Well, uhm. Sounds like accepting TabStaff by default might be sensible
>> to do?
>
> Why would anyone need a TabStaff within a ChoirStaff? That doesn’t
> make sense and I’m sure the TabStaff shou
Aaron Whittington writes:
> Bug has mysteriously disappeared. It just took an extraordinarily long time
> to generate the pdf.
This is typical for a font cache problem. Particularly in connection
with upgrades/reinstallations.
--
David K
ch I
> believe have different Unicode character properties)?
\lyricmode does not mean "Paste arbitrary text here".
LilyPond intentionally uses exclusively the ASCII character range for
syntactic purposes. Everything else can be part of identifiers or
words. That makes LilyPond documents rob
d e} ~e8 d16 c16 }
works on current master. But it's not exactly recommended syntax. Why
don't you write
{ \times 2/3 {c8 d e~ } e8 d16 c16 }
instead?
--
David Kastrup
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
what's actually put into the printed notation (particularly so when
printing full fractions instead of just the numerator).
--
David Kastrup
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
Federico Bruni writes:
> Hi
>
> I don't think these changes need a full review and I don't have time
> to go through it anyway.
> So find attached a patch to fix two minor issues. It applies to the
> stable/2.20 branch.
;(2 . 3) c'
For that reason, \tweak-like expressions generally take the music
expression to be tweaked as their last argument. That makes nesting
them reasonably clean.
--
David Kastrup
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
Malte Meyn writes:
> Am 23.03.2018 um 12:47 schrieb David Kastrup:
>> Malte Meyn writes:
>>
>>> Hi list,
>>>
>>> is there a reason for the special order of \offset arguments? I would prefer
>>> \offset Beam positions #'(2 . 3)
>
eople would use it a lot.
You could likely write
\offset Beam.positions #'(2 . 3) #'()
at the current point of time. Which is similarly ugly. Or
\offset Beam.positions #'(2 . 3) Bottom
which seems weird. You get the drift.
--
David Kastrup
underpinned by David's evaluations.
> But I find it very interesting that it takes significantly less time if you
> replace the s4. by an R4.
s4. can be condensed almost arbitrarily. You can fit several dozens of
measures in one line then if you want to.
--
David Kastrup
__
ld appear to me that
2 |
:|:
4 |
would be wrong, for example.
--
David Kastrup
___
bug-lilypond mailing list
bug-lilypond@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-lilypond
>
>>> Later in the chapter there is a snippet which demonstrates this.
>>
>> Not sure. It would appear to me that
>>
>> 2 |
>> :|:
>> 4 |
>>
>> would be wrong, for example.
>
> Here an example from Brahms Gesamta
t; (possibly with a picture)?
Meter changes should occur before an opening repeat sign. If there is a
closing one immediately adjacently, opening and closing one are placed
apart, and the meter change in between.
--
David Kastrup
___
bug-lilypond ma
are manual overrides (and style overrides
for a whole document), but the defaults should not require music
typesetting taste and choices.
--
David Kastrup
___
bug-lilypond mailing list
bug-lilypond@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-lilypond
ding to the available space.
>
> Now...are bowing instructions accents?
For the purposes of typesetting, I think they are. Except that in the
"order of accents", they are usually placed outermost IIRC.
--
David Kastrup
___
bug-lilypond mailing list
bug-lilypond@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-lilypond
o early
because of that (which caused me to look for the wrong bug in an input
file of mine).
--
David Kastrup
___
bug-lilypond mailing list
bug-lilypond@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-lilypond
Hi,
neither on gmane nor on mail-archive.org can I find a copy of my report
http://lists.gnu.org/archive/html/bug-lilypond/2009-10/msg00049.html>.
So what happened? Did the recent gmail outage lose reports for good on
most channels that people actually use?
--
David Kast
acket \center-column { "right" "y" } }
<>
--
David Kastrup
___
bug-lilypond mailing list
bug-lilypond@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-lilypond
801 - 900 of 1554 matches
Mail list logo
