The brace connecting the staves in PianoStaff context have the
wrong size.
can't duplicate. Probably an installation problem.
Hmm, I just checked lilypond with strace, and I can't find anything
suspicious. Similarly, the compilation and installation process (from
scratch, as usual) was
Graham Percival wrote:
On 30-Aug-05, at 3:38 AM, Hans de Rijck wrote:
6.5.1 Articulations
In the chart showing all scripts available, can there be some spacing
between the words, they are now almost impossible to decipher, for
example
the third line reads:
On 8/31/05, Mats Bengtsson [EMAIL PROTECTED] wrote:
Graham Percival wrote:
snip
I'm reluctant to do this, because it has a different musical meaning (ie
the
decresc starts on the c, not the d). Currently the manual example
demonstrates
the way lilypond handles most cresc/decresc.
Hi,
I have noticed a few things, possibly bugs, in a score I recently
typeset using 2.7.8 that didn't exist in a pdf I previous typeset
with Lilypond (not sure which version, sorry!). Here are some
examples - all examples are 2.7.8 vs. a previous version:
vs
As you can see, the tie
Context-first \change commands prior to any note, rest or skip data
print warning: can't change `Staff' to `down': not changing to same
context type and fail to effect staff change, as reported by Will
Oram.
% BEGN FIRST-NOTE CHANGE SNIPPET %%%
\score {
\context PianoStaff = piano
On 31-Aug-05, at 5:55 AM, Mats Bengtsson wrote:
Graham Percival wrote:
I'm accepting suggestions. This example is created from
input/test/script-chart.ly ;
the names are done as lyrics. How can you space out lyrics ?
According to the documentation, you might get the impression that
On 31-Aug-05, at 5:55 AM, Mats Bengtsson wrote:
I'm reluctant to do this, because it has a different musical meaning
(ie the
decresc starts on the c, not the d). Currently the manual example
demonstrates
the way lilypond handles most cresc/decresc. I think the best way to
handle this is to
