I am assuming that the regression tests are automatically converted
from time to time. But the allfontstyle. lyinc file seems to have
missed automatic conversion. This causes failures in the creation of
the web documentation.
--
Michael Welsh Duggan
([EMAIL PROTECTED])
___
[EMAIL PROTECTED] writes:
> I don't know Scheme, so I'm following blindly here. I tried it and got:
>
yes, it's for .37, not earlier versions.
--
Han-Wen Nienhuys | [EMAIL PROTECTED] | http://www.xs4all.nl/~hanwen
___
Bug-lilypond mailing
I don't know Scheme, so I'm following blindly here. I tried it and got:
Backtrace:
In /Users/spamguy/violink/flauti.ly:
19: 0* [ly:export ...
19: 1* [mmrest-of-length #]
13: 2 (let ((skip #)) (ly:music-compress skip (ly:music-length
mus)) skip)
17: 3* (ly:music-compress skip (ly:music
[EMAIL PROTECTED] writes:
> OK, pretty sure this is a bug in 2.1.35 (as opposed to StemUp :P).
>
> If the Devnull context is supposed to discard all musical info given to
> it, it doesn't.
>
> Assume myMusic = \notes {...} has polyphony on a single staff in it.
> Naturally, calling \myMusic wor
OK, pretty sure this is a bug in 2.1.35 (as opposed to StemUp :P).
If the Devnull context is supposed to discard all musical info given to
it, it doesn't.
Assume myMusic = \notes {...} has polyphony on a single staff in it.
Naturally, calling \myMusic works fine. BUT, doing this:
\context Devn
That's ok, because the syntax has changed:
instead of
\include "paper16.ly"
now you must use
#(set-global-staff-size 16)
convert-ly will do the change
Greetings,
Bert
___
Bug-lilypond mailing list
[EMAIL PROTECTED]
http://mail.gnu.org/mailman/
This has been around since 2.0? Wow. I've been using lily since 1.8 and
never encountered this problem. Better I learn eventually, I guess.
Best,
Will
On Mar 31, 2004, at 11.51 AM, Mats Bengtsson wrote:
Each \stemBoth only reverts one \stemDown or \stemUp, so if you want
to revert both, you sho
I installed the 2.1.31 version today. When I tried to run the new version against a
.ly file that worked with the previous version, I get a message that the "paper16.ly"
file could not be found. It looks like the directory containing these files is not
included in the 2.1.31 install.
Randy
Each \stemBoth only reverts one \stemDown or \stemUp, so if you want
to revert both, you should do
\stemUp ... \stemBoth\stemDown ... \stemBoth
or \stemUp ... \stemDown ... \stemBoth\stemBoth
You didn't say if you use version 2.0 or 2.1. For 2.0, this is described
at
http://lilypond.org/doc/v2.0/
I had to force some stems to point up or down. I couldn't revert back
to automatic stemming after I was done, so everything after the command
is operating off \stemUp.
Here's where I first started observing it:
\stemUp a)[ \stemDown gsharp''']( \stemBoth a)[ < bsharp,, e >]( <
csharp e >)[ < b
At 01:54 PM 3/31/2004 +0200, you wrote:
>Right! However, it's a good idea to teach already the beginners to
>include a \version statement in their files and refer to convert-ly
>as a motivation.
>Still, it's fairly common that people on the mailing list haven't
>noticed that convert-ly is available
The second bar of the first staff is identical to the first bar of the second
staff, yet they are typeset differently. The first staff switches between
chord and polyphony notation too often.
\score {
<<\new Staff \notes {
\partcombine
\relative c'' {r1 e8 f ~ f d}
\relative c' {c4 c c c e8
Right! However, it's a good idea to teach already the beginners to
include a \version statement in their files and refer to convert-ly
as a motivation.
Still, it's fairly common that people on the mailing list haven't
noticed that convert-ly is available, so we should try to highlight
it more.
/
Han-Wen Nienhuys writes:
> [EMAIL PROTECTED] writes:
>> In my opinion, convert-ly should be mentioned in the Tutorial.
>> Now the information is hidden in the section on converters from
>> other more or less obscure formats (and in the FAQ).
>
> What makes you think that users that already know li
On Wednesday 31 March 2004 12.11, Han-Wen Nienhuys wrote:
> [EMAIL PROTECTED] writes:
> > hi!
> >
> > I've been able to isolate the partcombine brokenness. Here's a score
> > demonstrating it:
>
> can you verify that this is fixed in CVS?
yes, it works now. thanks!
Erik
___
[EMAIL PROTECTED] writes:
> In my opinion, convert-ly should be mentioned in the Tutorial.
> Now the information is hidden in the section on converters from
> other more or less obscure formats (and in the FAQ).
What makes you think that users that already know lilypond will read
the tutorial?
--
In my opinion, convert-ly should be mentioned in the Tutorial.
Now the information is hidden in the section on converters from
other more or less obscure formats (and in the FAQ).
/Mats
chip wrote:
I am using freebsd and have been using lilypond-2.0.2 from the freebsd
ports. I am now installin
[EMAIL PROTECTED] writes:
>
> There's one situation I find curious though. The following scores have
> different music but produce the same paper output:
>
> \score {\notes \relative c'' \partcombine
> {g4 g a( b) c c r r}
> {g4 g r4 r e e g g}}
> \score {\notes \relative c'' \partcombine
> {g4
[EMAIL PROTECTED] writes:
>
>
> Also, I still find the docu a bit confusing, since the 'up stems' implicitly
> refers to a situation that never is mentioned. I'd suggest to add half a bar
> of polyphony in the first example (like the example from my last bugreport),
> and maybe rewrite the sec
On Wednesday 31 March 2004 10.42, Han-Wen Nienhuys wrote:
> [EMAIL PROTECTED] writes:
> > > >c-part-combining.html#Automatic% 20part%20combining
> > > > In the first example, the stems of the two voices are merged.
> > > > According to the documentation they shouldn't be.
> > >
> > > Why?
> >
> > W
[EMAIL PROTECTED] writes:
> Hi,
>
> In the following example, the first note is typeset as a chord , though
> the parts are unison.
>
> \version "2.1.36"
> \score {\notes \relative c''
> \partcombine
> {g4 g a( b) c c r r d e}
> {g,4 g r4 r e e g g a2 }
> }
I added a remark to the manual. \pa
Hi,
In the following example, the first note is typeset as a chord , though
the parts are unison.
\version "2.1.36"
\score {\notes \relative c''
\partcombine
{g4 g a( b) c c r r d e}
{g,4 g r4 r e e g g a2 }
}
erik
___
Bug-lilypond mailing list
[
[EMAIL PROTECTED] writes:
> hi!
>
> I've been able to isolate the partcombine brokenness. Here's a score
> demonstrating it:
can you verify that this is fixed in CVS?
--
Han-Wen Nienhuys | [EMAIL PROTECTED] | http://www.xs4all.nl/~hanwen
hi!
I've been able to isolate the partcombine brokenness. Here's a score
demonstrating it:
\score {
\new Staff \notes {a1*8 \partcombine \X \Y}
}
\paper{}
}
Insert just about any music as \X and \Y. All decisions about how to arrange
the voices will be offset by 8 bars; thus strange things
Stanislav Brabec writes:
Hi,
> Here are SuSE fixes for lilypond.
>
> lilypond-2.0.3.patch: Fixed info pages, one include and one line in
> configure.in.
> lilypond-2.0.3-autogen.patch: Fixes autogen.sh.
This suggests that you have two patches for us, in addition to the
find + SED script.
Howeve
[EMAIL PROTECTED] writes:
> > >c-part-combining.html#Automatic% 20part%20combining
> > > In the first example, the stems of the two voices are merged. According
> > > to the documentation they shouldn't be.
> >
> > Why?
>
>
> What exactly happens if the two parts differ? Will they (1) always be m
26 matches
Mail list logo
