On Aug 17, 2005, at 1:23 AM, Graham Percival wrote:
BTW, why are you using R1*3/4*x ? Why not simply use R2.*3/4 ?
Do you mean R2.*x? The latter is some single-unit rest of unpleasant
duration, I think.
To answer your question, no reason -- strange old habit. Good as time
as any to switc
On 16-Aug-05, at 6:53 AM, Nathan Curry wrote:
I've set up lilypond 2.6 for my client, and after reviewing the new
documentation, here are his issues:
Unfortunately bug-lilypond removes attachments (the text of your email
suggests that you tried to send some). Could you split these problem
r
On 16-Aug-05, at 10:01 PM, Will Oram wrote:
It's getting better, but lilypond sometimes just leaves bars in
combined part lines blank. An example:
Interesting; it's prompted by using R1*x. In this smaller example,
using the
second "two" definition (which avoids R1*x), it works just fine.
On 16-Aug-05, at 8:03 PM, D Josiah Boothby wrote:
Using the 2.6.0 autopackage on Debian sarge/sid, Evince (v. 0.3.0)
doesn't display the 3's in the time signatures.
Please file a bug report with evince, then. (?)
___
bug-lilypond mailing list
bu
It's getting better, but lilypond sometimes just leaves bars in
combined part lines blank. An example:
partA = {
\clef "treble"
\key eflat \major
\time 6/8
R1*3/4*2
r8 d8\p(\< eflat f aflat4)~\!
aflat4.\fermata\mf~\> aflat8\pp\! r
Using the 2.6.0 autopackage on Debian sarge/sid, Evince (v. 0.3.0)
doesn't display the 3's in the time signatures.
An example .ly file:
\version "2.6.0"
\score {
\relative c' {
\time 3/4 d2.
\time 7/8 e2..
\time 2/4 f2
\time 3/8 es4.
\time 5/8 ges4 f4.
\time 4/8 e2
\time
On 16-Aug-05, at 12:19 PM, Peter Teeson wrote:
It appears that the fink packages are way out of date.
Even the unstable devel version is only at 2.5.23
So just what's the point of doing things the fink way if it is so far
behind?
There's more up-to-date packages in fink 0.8 (which is only fo
On 16 Aug 2005, at 23:54, Erik Sandberg wrote:
On Tuesday 16 August 2005 22.54, Hans Aberg wrote:
But TeX was developed once, too. Its author got tired, putting the
lid on further development, having the copyright. It could happen
with LilyPond, too, if one arrives the point where one has the
Thank you Kris.
I am aware of the .dmg.
But that is merely an install.
I want to build from scratch for a number of reasons.
respect...
Peter
On Aug 16, 2005, at 15:41, Kris Shaffer wrote:
The most "straightforward way" to build Lilypond on Mac OS X now is to
download the DMG package directly f
On Tuesday 16 August 2005 22.54, Hans Aberg wrote:
> But TeX was developed once, too. Its author got tired, putting the
> lid on further development, having the copyright. It could happen
> with LilyPond, too, if one arrives the point where one has the
> reached limits of the current setup.
This i
On 16 Aug 2005, at 15:18, Erik Sandberg wrote:
The comparison between TeX/LaTeX and Lilypond is not completely
relevant.
Lilypond uses a different development model. You can see the
current lilypond
as a less generic TeX, with most of LaTeX's functionality hardcoded
into it.
Lily is gradua
Fairchild wrote:
Suggest adding "Postscript strings are ignored by the dvi viewer." to the
\postscript definition in the overview of text markup commands.
DVI is deprecated for 2.6 anyway.
--
Han-Wen Nienhuys - [EMAIL PROTECTED] - http://www.xs4all.nl/~hanwen
__
Suggest adding "Postscript strings are ignored by the dvi viewer." to the
\postscript definition in the overview of text markup commands.
-Original Message-
From: Bertalan Fodor [mailto:[EMAIL PROTECTED]
Sent: Tuesday, August 16, 2005 1:44 PM
To: bug-lilypond; Fairchild
Subject: Re: Embed
Previously I had DL'd the 2.6.3 tarball and was working through
building it on Panther 10.3.9
Based on Graham's comments I tried to do things the way other Mac folks
do.
So I downloaded and installed fink and fink commander.
It appears that the fink packages are way out of date.
Even the unstabl
It's normal. The dvi viewer does not interpret any postscript.
Bert
This snippet, adapted from the documentation, doesn't produce the text in
the dvi file. The ps and pdf are OK.
%%
\version "2.4.6"
\score { {
c''1_\markup { \postscript #" 4 -4 moveto /Times-Roman
This snippet, adapted from the documentation, doesn't produce the text in
the dvi file. The ps and pdf are OK.
%%
\version "2.4.6"
\score { {
c''1_\markup { \postscript #" 4 -4 moveto /Times-Roman findfont 3.0
scalefont setfont 90 rotate (hello) show " } } }
Am 13.08.05 schrieb TinneyHeath:
> I have tried to install Lilypond version 2.7.4 on a sytem running SuSE
> 9.0, using the any x86 autopackage. I get a failure message that says
> that it cannot find "Python Language Runtime". I have no package of
> this name on my distro. I tried installing th
On Tuesday 16 August 2005 09.37, Daniel McLaury wrote:
> I'm running Lilypond 2.7.4 and trying to use a cautionary accidental.
> I'm not sure what exactly the problem is -- in the PS output file the
> cautionary accidental is rendered correctly; in the PDF the parens are
> in the correct place, to
On Mon, 15 Aug 2005 17:06:51 +0200, Erik Sandberg
<[EMAIL PROTECTED]> wrote:
On Monday 15 August 2005 17.30, Yuval Harel wrote:
On Sun, 14 Aug 2005 23:53:12 +0200, Erik Sandberg
<[EMAIL PROTECTED]> wrote:
> You're right. I don't have working sound right now, so I relied on
> midi2ly
> which
I'm running Lilypond 2.7.4 and trying to use a cautionary accidental.
I'm not sure what exactly the problem is -- in the PS output file the
cautionary accidental is rendered correctly; in the PDF the parens are
in the correct place, to the left of the notehead, and the accidental is
displayed
I've set up lilypond 2.6 for my client, and after reviewing the new
documentation, here are his issues:
If you invoke the 20 \mm line, the result will indent the music 20 mm
and place the instrument names accordingly. However in a .tex file,
the indent function, whether it's default or invoked for
On Tuesday 16 August 2005 11.54, Hans Aberg wrote:
> On 16 Aug 2005, at 10:03, Mats Bengtsson wrote:
> >> I figure so. But I do not know the worth of the effort of
> >> pursuing it. One can perhaps draw a parallel to the TeX macro
> >> package LaTeX, which in its original form was too rigid for
>
I finally found the silly bug causing the problem. The fix will
appear in next versions of 2.6.x and 2.7.x.
It's also easy to fix it yourself in your existing installation.
Just open /usr/bin/lilypond-book (or wherever the program is installed,
check with 'which lilypond-book') in a text editor (a
On 16 Aug 2005, at 13:06, Han-Wen Nienhuys wrote:
When I it, I get:
~/Development/tmp2 foo$ /Applications/LilyPond.app/Contents/
Resources/ bin/fondu /Library/Fonts/Verdana
Can't find an appropriate resource fork in /Library/Fonts/Verdana
So it seems, that for some reason, it does not work unde
Hans Aberg wrote:
On 15 Aug 2005, at 23:28, Han-Wen Nienhuys wrote:
Fondu is in the bundle. Can you see what happens when you do
LilyPond.app/Contents/Resources/bin/fondu \
/Library/Fonts/Verdana
this should leave a couple of ttf files in the working directory
When I it, I get:
~/Develo
On 15 Aug 2005, at 23:28, Han-Wen Nienhuys wrote:
Fondu is in the bundle. Can you see what happens when you do
LilyPond.app/Contents/Resources/bin/fondu \
/Library/Fonts/Verdana
this should leave a couple of ttf files in the working directory
When I it, I get:
~/Development/tmp2 foo$ /Appl
On 16 Aug 2005, at 10:03, Mats Bengtsson wrote:
I figure so. But I do not know the worth of the effort of
pursuing it. One can perhaps draw a parallel to the TeX macro
package LaTeX, which in its original form was too rigid for
general use, and too difficult to reprogram; therefore, in p
Here's one of the bugs database; the glissando line doesn't stop before
an accidental. I don't consider it a very serious bug, though.
Workaround:
\once \override Glissando #'gap = #0.5
\once \override Glissando #'extra-offset = #'(-0.5 . 0)
produces a gliss which does an (IMO) acceptable jo
Hans Aberg wrote:
On 15 Aug 2005, at 15:21, Mats Bengtsson wrote:
My conclusion here is that LilyPond can never be expected to provide
automatic support to handle all special cases of information that
people might want to squeeze into the title of a piece, not to mention
all possible layouts.
29 matches
Mail list logo
