[EMAIL PROTECTED] writes:
> On Saturday 25 September 2004 20.36, Graham Percival wrote:
> > On 24-Sep-04, at 2:31 AM, Han-Wen Nienhuys wrote:
> > > [EMAIL PROTECTED] writes:
> > >> Add boxed-rehearsal-mark to this. It is now worse than in 2.2, the
> > >> bottom line
> > >> is way off. see attachmen
[EMAIL PROTECTED] writes:
> Hi!
>
> Once Score.SystemStartBracket #'transparent has been overridden to ##t, it
> seems it is not possible to revert the effect. For an example, look at
> section 3.4.2 in the manual (in recent CVS; this is not yet on the web
> site) or, respectively, in the gene
On Saturday 25 September 2004 20.36, Graham Percival wrote:
> On 24-Sep-04, at 2:31 AM, Han-Wen Nienhuys wrote:
> > [EMAIL PROTECTED] writes:
> >> Add boxed-rehearsal-mark to this. It is now worse than in 2.2, the
> >> bottom line
> >> is way off. see attachment.
> >
> > There is something very fis
On 24-Sep-04, at 2:31 AM, Han-Wen Nienhuys wrote:
[EMAIL PROTECTED] writes:
Add boxed-rehearsal-mark to this. It is now worse than in 2.2, the
bottom line
is way off. see attachment.
There is something very fishy with this one. The -f ps version is
perfect, as is the -f tex. Only when used throu
On 23-Sep-04, at 3:06 AM, Juergen Reuter wrote:
The example templates in section 3 of the manual
(Documentation/user/examples.itely) currently contain a '\version
"2.3.16"' header. Shouldn't this header be automatically inserted when
dissecting the .itely file?
\version info isn't inserted automat
The docs suggest that if you \partcombine two voices (and they
have different notes), the stems will be in different directions. The
following example (taken from the docs) have the two different
parts joined by a single stem. Are the docs in error, or is this
a bug?
\relative c'' {
\new Staff \p
Hi!
Once Score.SystemStartBracket #'transparent has been overridden to ##t, it
seems it is not possible to revert the effect. For an example, look at
section 3.4.2 in the manual (in recent CVS; this is not yet on the web
site) or, respectively, in the generated file
Documentation/user/out-www/
> I'm now convinced that it is a bug, and I've sent a report to
> bug-lilypond.
Two bug reports are sitting in the queue (I thought that I can
directly send attached PNG images as a subscribed list member, ...)
Werner
___
lilypond-devel mailing
> \transposition d'
> ...
>
> It is the last command which worries me. The d' looks very
> unnatural:
I'm now convinced that it is a bug, and I've sent a report to
bug-lilypond.
Werner
___
lilypond-devel mailing list
[EMAIL PROTECTED]
Even after looking into stem.cc I don't know how the various stem
length parameters interact. Can someone please explain how exactly
the stem length is computed from the parameters
lengths
stem-shorten
beamed-lengths
beamed-minimum-free-lengths
beamed-extreme-minimum-free-lengths
The
Nicolas Sceaux <[EMAIL PROTECTED]> writes:
> My mistake.
> pango 1.4.1 was the debian's one. I have 1.5.0 from (old) CVS. This is the
> one that was used to compile LilyPond with --enable-gui.
> I am upgrading to pango 1.5.2.
>
> What does BLOEDIGE_RAND mean? bleeding edge?
> Should I use pango, g
Jan Nieuwenhuizen <[EMAIL PROTECTED]> writes:
> Nicolas Sceaux writes:
>
>>> That's quite strange. I tested on a fresh machine. What versions of
>>> fontconfig/gnome/pango do you use?
>>
>> fontconfig is version 2.2.3
>> gnome is 2.6.1
>> pango is 1.4.1
>>
>> ohoh, maybe I should look at guile-
Consider a trumpet 1 in B flat (\tri), quoting trumpet 2 in B flat
(\trii). Both voices are entered normally (that is, in C). To make
this work, I have to say
in trumpet1.ly:
\addquote "trii \trii
\transpose bes c' \tri
in \tri:
...
\quote "trii" ...
...
in \t
Nicolas Sceaux writes:
>> That's quite strange. I tested on a fresh machine. What versions of
>> fontconfig/gnome/pango do you use?
>
> fontconfig is version 2.2.3
> gnome is 2.6.1
> pango is 1.4.1
>
> ohoh, maybe I should look at guile-gnome.sh again, and get a more
> recent pango. I'm doing t
14 matches
Mail list logo
