Re: Patch to make building 2.4.5 debian package work
Roman Stöckl-Schmidt writes: I'm far from what you'd call a wizard, so what I came up with is very probably NOT a clean fix, but it works. So here's the patch. Thanks, applied. Jan. -- Jan Nieuwenhuizen [EMAIL PROTECTED] | GNU LilyPond - The music typesetter http://www.xs4all.nl/~jantien | http://www.lilypond.org ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
'make all' failure ChangeLog 1.3358
Just tried again and got:
-e '[EMAIL PROTECTED]@!/usr/src/lilypond/stepmake/bin!g' out/lilypond-
pdfpc-helper
chmod 755 out/lilypond-pdfpc-helper
/usr/bin/perl /usr/src/lilypond/buildscripts/out/help2man out/lilypond-
pdfpc-helper out/lilypond-pdfpc-helper.1
true
true
make[1]: Leaving directory `/usr/src/lilypond/scripts'
make[1]: Entering directory `/usr/src/lilypond/elisp'
cd /usr/src/lilypond /usr/bin/python buildscripts/lilypond-words.py
--el --dir=/usr/src/lilypond/elisp/out
Traceback (most recent call last):
File buildscripts/lilypond-words.py, line 27, in ?
F = open('scm/new-markup.scm', 'r')
IOError: [Errno 2] No such file or directory: 'scm/new-markup.scm'
make[1]: *** [out/lilypond-words.el] Error 1
make[1]: Leaving directory `/usr/src/lilypond/elisp'
make: *** [all] Error 2
[EMAIL PROTECTED] lilypond]#
-David
Fedora Core 3
___
lilypond-devel mailing list
lilypond-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: 'make all' failure ChangeLog 1.3358
David Bobroff writes: Just tried again and got: Thanks (2x), both fixed. Jan. -- Jan Nieuwenhuizen [EMAIL PROTECTED] | GNU LilyPond - The music typesetter http://www.xs4all.nl/~jantien | http://www.lilypond.org ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: lilypond/debian rules
Jan Nieuwenhuizen wrote:
CVSROOT:/cvsroot/lilypond
Module name:lilypond
Branch:
Changes by: Jan Nieuwenhuizen [EMAIL PROTECTED] 05/03/30 08:39:38
Modified files:
debian : rules
Log message:
CVSWeb URLs:
http://savannah.gnu.org/cgi-bin/viewcvs/lilypond/lilypond/debian/rules.diff?tr1=1.44tr2=1.45r1=textr2=text
Patches:
Index: lilypond/debian/rules
diff -u lilypond/debian/rules:1.44 lilypond/debian/rules:1.45
--- lilypond/debian/rules:1.44 Wed Oct 13 11:55:01 2004
+++ lilypond/debian/rules Wed Mar 30 08:39:38 2005
@@ -125,7 +125,7 @@
-exec cp -a --parents '{}' $(r_data)/$(d)/examples ';'
dh_installchangelogs
- mv $(r_data)/usr/share/lilypond/$(VERSION)/dvips/lilypond.map \
+ mv $(r_data)/usr/share/lilypond/$(VERSION)/fonts/map/lilypond.map \
$(r_data)/etc/texmf/dvips/lilypond.map
Why not install it in .../texmf/fonts/map/ ? As far as I know, that
should work
already with teTeX 2 and makes it future proof for teTeX 3 as well.
/Mats
___
lilypond-devel mailing list
lilypond-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: lilypond/debian rules
Mats Bengtsson writes: Why not install it in .../texmf/fonts/map/ ? Good question. That would require an additional symlink in the texmf tree, though. Debian's experimental tetex-3.0 installs map files in /etc/texmf/map/dvips/ Jan. -- Jan Nieuwenhuizen [EMAIL PROTECTED] | GNU LilyPond - The music typesetter http://www.xs4all.nl/~jantien | http://www.lilypond.org ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
@documentencoding utf-8?
Hi, The development release of LilyPond has switched to utf-8 encoding throughout (LilyPond music source, documentatiton, website). Any chance for @documentencoding utf-8 to be implemented in texinfo soonish? Greetings, Jan. -- Jan Nieuwenhuizen [EMAIL PROTECTED] | GNU LilyPond - The music typesetter http://www.xs4all.nl/~jantien | http://www.lilypond.org ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: 'make all' failure ChangeLog 1.3357
Oops. Sorry about that; thanks for the quick fix, Jan. -Dave Jedlinsky From: David Bobroff [EMAIL PROTECTED] Date: Wed, 30 Mar 2005 07:03:06 + The subject line says it all. 'make all' output this before giving up: -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include- I/usr/include/freetype2 -W -Wall -Wconversion -o out/general-scheme.o general-scheme.cc general-scheme.cc:17:39: utf8/wchar.h: No such file or directory general-scheme.cc: In function `scm_unused_struct* ly_wchar_to_utf_8 (scm_unused_struct*)': general-scheme.cc:226: error: `mbstate_t' undeclared (first use this function) general-scheme.cc:226: error: (Each undeclared identifier is reported only once for each function it appears in.) general-scheme.cc:226: error: expected `;' before state general-scheme.cc:227: error: `state' undeclared (first use this function) general-scheme.cc:230: error: `wcrtomb' undeclared (first use this function) make[1]: *** [out/general-scheme.o] Error 1 make[1]: Leaving directory `/usr/src/lilypond/lily' make: *** [all] Error 2 [EMAIL PROTECTED] lilypond]# -David Fedora Core 3 ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
autoBeamOff bug
There seems to be a bug in \autoBeamOff. If it is issued in the
middle of a sequence of notes that would be beamed together, it
doesn't take effect until after the end of that group. It seems that
the correct behavior should be to stop automatic beaming at the point
where the command is issued. It poses a particular problem for me
with some (partially) generated input.
Here's an example showing the problem:
\version 2.5.15
\score {
\relative c' {
\autoBeamOn d'8 cis d b cis b cis ais |
b ais b d~ d \autoBeamOff cis d b |
}
}
The final d cis d b sequence is beamed in the current code, but it
shouldn't be.
Thanks,
Russ
___
lilypond-devel mailing list
lilypond-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: text crescendo
On 27-Mar-05, at 3:58 PM, Han-Wen Nienhuys wrote:
[EMAIL PROTECTED] writes:
That's useful info, but why is
\cresc c
equivalent to
c \setTextCresc \
? Why not go with a postfix \cresc?(thus \cresc =
\setTextCresc
\ )
IMO, the hairpin and the cresc - - - are two styles of conveying the
same information, so they should entered with in the same way ( \
). Style settings are property settings, which should occur before
the note is started.
Yes, they should be entered the same way -- that's my objection to
\cresc. These lines produce the same thing:
{
c'4 c'\ c'\! c'
c'4 \cresc c' c'\! c'
}
but on the first line, you do \ after the note, while on the second
line,
you do \cresc *before* the note.
From a programming standpoint, I don't think we should have any
#(ly:export (make-event-chord (list cr)))
in ly/spanners-init.ly ; it messes up the postfix idea. Just like we
changed slurs from (a b) to a( b), I think we should change
\cresc a b\! to a\cresc b\!
Cheers,
- Graham
___
lilypond-devel mailing list
lilypond-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: lilypond Documentation/user/invoking.itely ./Ch...
On 27-Mar-05, at 3:28 AM, Han-Wen Nienhuys wrote:
[EMAIL PROTECTED] writes:
On 9-Mar-05, at 6:14 PM, Han-Wen Nienhuys wrote:
[EMAIL PROTECTED] writes:
[EMAIL PROTECTED] Preparing the jail
- snip old version -
Dvips does not apply to lily 2.5. The PS backend does not use the TeX
installation.
How's this?
@item Preparing the jail
LilyPond needs to read a number of files while running. All these
files
are to be copied into the jail, under the same path they apper in the
real root filesystem. The entire content of the LilyPond installation
(e.g., @file{/usr/share/lilypond})
should be copied.
You have to discuss this with Seba. 2.5 also needs to read various
font directories, and I don't know how thi s interacts with the jail.
Sebastino? This is the version that's in the manual right now; is it
accurate? I removed references to TeX stuff, but I don't know much
about lilypond's backend, so I might have removed too much.
Cheers,
- Graham
___
lilypond-devel mailing list
lilypond-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-devel
point and click
Not that I ever use it, but point and click (in pdfs) isn't working on
OSX. Fink, 2.5.17.
Input file:
\version 2.5.17
{ c'4 }
ps contains mark_URI, but the pdf does not. Here's the tail of
lilypond -V foo.ly
-
Optimal demerits: 103.495995
Element count 40.[0]Calculating page
breaks...[century_schoolbook_l__3.865234375]programming error:
Stencil::moved_to_edge: adding empty stencil.
Continuing; crossing fingers
Layout output to `foo.ps'...
[/sw/share/lilypond/2.5.17/ps/music-drawing-routines.ps][/sw/share/
lilypond/2.5.17/ps/lilyponddefs.ps][/sw/share/lilypond/2.5.17/ps/
emmentaler-20.cff.ps]Converting to `foo.pdf'...Invoking `ps2pdf
-sPAPERSIZE=a4 'foo.ps''...
]spark:~/tmp gperciva$
Does ps2pdf need some special arguments to keep the mark_URI ?
Cheers,
- Graham
___
lilypond-devel mailing list
lilypond-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: @documentencoding utf-8?
chance for @documentencoding utf-8 to be implemented in texinfo soonish? Not by me. Sorry. Patches would be more than welcome, of course. (Doing the fonts in TeX is an especially large piece of the problem, although even having support in makeinfo alone would be terrific. I don't think it will be easy.) ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
PATCH: Colors for the TeX backend
Hi, Here's color support for the TeX backend too. Tested on MacOSX. I'll do the SVG backend sometime this weekend. Erlend texcolor.patch Description: Binary data ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
