Paul Scott <[EMAIL PROTECTED]> writes:
> Kilian A. Foth wrote:
>
>>Paul Scott writes:
>> > Kilian A. Foth wrote:
>> > > >Greetings,
>> > >
>> > >a while back I asked lilypond-user how to engrave a tie between
>> > >enharmonic variants, such as g sharp in one bar and a flat in the next
>> > >after
fails with
! Undefined control sequence.
l.1 \includegraphics
{lily-203923813-1.eps}%
I don't really know how lilypond-book and latex live together; here's
my commands and output.
simple.lytex:
-
\documentclass[]{article}
\begin{document}
Normal LaTeX text.
\begin{lilypond}
> It would be wonderful to have this in the distribution.
This is the final goal.
> * convert parmesan (I suspect this might be a lot of work. Many of
>the glyphs use pens)
I'll do that slowly.
> * convert feta-alphabet (should be easy - they're already outline
>based)
This is my ne
Paul Scott writes:
> Kilian A. Foth wrote:
>
> >Greetings,
> >
> >a while back I asked lilypond-user how to engrave a tie between
> >enharmonic variants, such as g sharp in one bar and a flat in the next
> >after a key change. The reponse was that not only does lilypond not do
> >this, but
Kilian A. Foth wrote:
Paul Scott writes:
> Kilian A. Foth wrote:
>
> >Greetings,
> >
> >a while back I asked lilypond-user how to engrave a tie between
> >enharmonic variants, such as g sharp in one bar and a flat in the next
> >after a key change. The reponse was that not only does lilypond not d
Hello, I wanted to contribute a patch for nicer slurs, but I don't
really know how to do it.
I've found that dashed slurs are quite ugly. That's because
output-ps.scm sets the dash length to the property Slur.dashed, but the
gap between dashes is set to 10*slur.thickness, that is not good. I've
[EMAIL PROTECTED] writes:
>
> Greetings,
>
> a while back I asked lilypond-user how to engrave a tie between
> enharmonic variants, such as g sharp in one bar and a flat in the next
> after a key change. The reponse was that not only does lilypond not do
> this, but you cannot even typeset the ti
Kilian A. Foth wrote:
Greetings,
a while back I asked lilypond-user how to engrave a tie between
enharmonic variants, such as g sharp in one bar and a flat in the next
after a key change. The reponse was that not only does lilypond not do
this, but you cannot even typeset the tie manually by \overr
Greetings,
a while back I asked lilypond-user how to engrave a tie between
enharmonic variants, such as g sharp in one bar and a flat in the next
after a key change. The reponse was that not only does lilypond not do
this, but you cannot even typeset the tie manually by \overriding
something. I w
[EMAIL PROTECTED] writes:
> > * Maybe it would be a good idea to have separate snippet DB for each
> > branch (ie. a 2.4 and 2.6 database.). It is possible to run
> > multiple versions of Lily alongside eachother. If you can't make
> > it work, that is a serious bug, and I will gladly
First of all, thanks to the surprisingly large number of people who
sent me feedback for the 2.5.9 packages.
I'm pleased to report that the 2.5.10 packages are now available and
installable using the same method. They appear to look even better than
2.5.9
Matthias
While 2.5.10 looks good (and fixes the many diagnostic messages I saw
with 2.5.9), there is a small flaw in the build: It assumes that the
package is already installed while it's being built, otherwise lily.scm
is not found.
This can be remedied with the following patch:
–
d
On Monday 31 January 2005 06.38, Graham Percival wrote:
> On 30-Jan-05, at 7:38 AM, Han-Wen Nienhuys wrote:
> > * Maybe it would be a good idea to have separate snippet DB for each
> > branch (ie. a 2.4 and 2.6 database.). It is possible to run
> > multiple versions of Lily alongside each
[EMAIL PROTECTED] writes:
> > Please keep me posted on your success /failure of reproducing these
> > instructions.
>
> I had to play a little with fink; it hadn't selected pango1-xft2 . But
> that could just be
> my setup.
>
>
> The new font (for c^"foo") looks a bit... "heavy"? Is it large
14 matches
Mail list logo
