more python build issues
When building from scratch, and after doing the
make -C python
trick, I end up with this build failure:
/usr/bin/python ../../../scripts/musicxml2ly.py -o
out/00a-Basics-Pitches.ly 00a-Basics-Pitches.xml
Traceback (most recent call last):
File "../../../scripts/musicxml2ly.py", line 1907, in ?
main()
File "../../../scripts/musicxml2ly.py", line 1902, in main
voices = convert (filename, options)
File "../../../scripts/musicxml2ly.py", line 1819, in convert
progress ("Reading MusicXML from %s ..." % filename)
File "../../../scripts/musicxml2ly.py", line 28, in progress
stderr_write (str + '\n')
NameError: global name 'stderr_write' is not defined
make[3]: *** [out/00a-Basics-Pitches.ly] Error 1
Is this a new python 2.5 feature?
Cheers,
- Graham
___
lilypond-devel mailing list
lilypond-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-devel
build requires manually calling make -C python
After deleting everything and doing ./autogen.sh make I get this: chmod 755 out/midi2ly /usr/bin/perl /home/lilypond/lilypond/buildscripts/out/help2man out/midi2ly > out/midi2ly.1 help2man: can't get `--help' info from out/midi2ly Running make -C python manually solves this issue. This is on a Debian/linux box, BTW. Cheers, - Graham ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
build failure with python 2.4.4
I can't build lilypond any more with python 2.4.4:
$ nice make
...
Traceback (most recent call last):
File "/home/lilypond/lilypond/scripts/lilypond-book.py", line
1872, in ?
main ()
File "/home/lilypond/lilypond/scripts/lilypond-book.py", line
1838, in main
chunks = do_file (file)
File "/home/lilypond/lilypond/scripts/lilypond-book.py", line
1696, in do_file
progress (_ ("Reading %s...") % input_fullname)
File "/home/lilypond/lilypond/python/out/lilylib.py", line 60,
in stderr_write
encoded_write (sys.stderr, s)
File "/home/lilypond/lilypond/python/out/lilylib.py", line 57,
in encoded_write
f.write (s.encode (f.encoding))
TypeError: encode() argument 1 must be string, not None
make[2]: *** [out/lilypond.nexi] Error 1
Cheers,
- Graham
___
lilypond-devel mailing list
lilypond-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-devel
Point and click for Lilypond in KDE (was: Re: patch for scm/editor.scm to add KDE (Kate) support.)
Because of the differences in Kate line numbering between KDE 3 and 4 I think it's better to handle the invocation of the editor inside KDE, bypassing lilypond-invoke-editor. So the patch I sent to lily-devel is not necessary. I created two very small files that do the job. Both are attached, with a README. Hopefully this will once become a simple LilyPond/KDE package, with a nice helper plugin for Kate I'm trying to create. with best regards, Wilbert Berendsen -- http://www.wilbertberendsen.nl/ "You must be the change you wish to see in the world." -- Mahatma Gandi ktexteditservice Description: application/shellscript [Protocol] exec=ktexteditservice %u protocol=textedit input=none output=none helper=true listing= reading=false writing=false makedir=false deleting=false Icon=txt Class=:local Lilypond Point and Click for KDE (3.x and 4.x) == Nederlandse uitleg (English see below): 1. Plaats textedit.protocol in de KDE-services map, bijvoorbeeld ~/.kde/share/services/ of /usr/share/services/. 2. Plaats ktexteditservice ergens in het systeempad, bijvoorbeeld ~/bin/ of /usr/local/bin/ en maakt het uitvoerbaar: chmod +x ktexteditservice Maak nu een Lilypond-bestand aan in Kate. Laat Lilypond een PDF aanmaken, open deze in KPDF en klik in de PDF op een muzieknoot. Voilá! English: 1. Put textedit.protocol somewhere in the KDE services directory, for example in ~/.kde/share/services/ or /usr/share/services/. 2. Put ktexteditservice somewhere in the system PATH, for example in ~/bin/ of /usr/local/bin/ and make it executable: chmod +x ktexteditservice Now create a .ly file with Kate. Run Lilypond and open the resulting PDF with KPDF. Click on music notes and see the cursor jump to the correct location! Note: Kate from KDE3 uses a different line numbering scheme than Kate from KDE4. Please (un)comment the corresponding lines in ktexteditservice. Contact: Wilbert Berendsen <[EMAIL PROTECTED]> http://www.wilbertberendsen.nl/ Wed Jan 30 15:35:23 CET 2008 ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: patch for scm/editor.scm to add KDE (Kate) support.
Op woensdag 30 januari 2008, schreef Wilbert Berendsen: > > Kate numbers lines starting with 0, so I had to add some code to decrease > the line number in the textedit:// url by one. The special string > %(line-1)s is replaced with the line number minus one. Well, I now discover Kate from KDE3 starts line and col numbering at 0, but Kate from KDE4 starts numbering lines and cols with 1. Lilypond's textedit:// URIs on the other hand, start line numbers with 1 and col and char numbers with 0. (If I understand correctly.) So I guess I better add a textedit protocol wrapper to KDE, so that it automagically converts the textedit:// uris to a correct call to Kate. If I can get the texteditprotocol handler part of KDE, it can abstract away the differences in line and col counting. Met vriendelijke groet, Wilbert Berendsen -- http://www.wilbertberendsen.nl/ "You must be the change you wish to see in the world." -- Mahatma Gandi ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: Postponed Bugs #83 and #297: "a Someone Else Problem"
On Tue, 29 Jan 2008, Han-Wen Nienhuys wrote:
2008/1/27, Juergen Reuter <[EMAIL PROTECTED]>:
The ligature events are implemented as 'command-event', like \bar and
\time, which fall in between the notes.This is inconsistent with
start/stop commands like [ ] , but I can't really judge if that is the
best way to do it.
Hmmh, I don't understand. In Lily 2.7.x, in define-music-types.scm,
LigatureEvent has "(types . (general-music span-event ligature-event
event))", i.e. it is a SpanEvent, or am I missing something? In Lily
2.11.x, it is implemented as StreamEvent, due to Erik's changes. How is
this related to "command-event" (which, btw, I could not find in the
sources)?
this distinction is not in the music 'type-system', but rather how the
events are attached to other things. Beam/slur/etc. start/stop are
attached to the notes, so in
c4]
the ] starts at the beginning of the note. Commands like \bar , \clef
and \] are not attached to notes, so for
c4 \]
the event registers at the end of the note, at the start of the new time-step.
Aah, ok, I see.
I don't know what the best solution is, but for consistency, it would
probably be best if they were attached to notes like beams.
Yes. Honestly speaking, I did not feel too much comfortable, when the
post attributes-like "c4[ c4]" kind of notation for slurs and beams was
introduced. But you are right, for the sake of consistency, ligature
notation probably should follow this approach, too (as already mentioned
in the docs, btw.).
The
downside to attaching to notes is that you would not be able to do
ligs = { \[ s2 \] }
<< { c8 d e f }
\ligs >>
and have the ligature enclose the 4 notes.
I think this is a non-issue, because having a ligature in one voice
definitely does not imply that there are simultaneous ligatures in other
voices. That is, in the above example, having the ligature enclose the 4
notes would actually be a bug. By the way, if you are using ligature
brackets, there should be only a single voice per staff anyway; otherwise,
the notation would easily become confusing for the human reader (i.e.
which ligature bracket belongs to which notes, etc.).
(Oh, you are right, it's difficult to find me on the web, since my old
home page unfortunately died a while ago; there is now a new one at
www.juergen-reuter.de).
maybe you can update the relevant web-pages? That would be a useful
exercise in git use :-)
You should claim sponsoring from the git guys for advertising and
spreading use of their piece of software among the lilypond community! :-)
Ok, I will eventually try, as soon as I find some time to browse through
the git docs!
Greetings,
Juergen
--
Han-Wen Nienhuys - [EMAIL PROTECTED] - http://www.xs4all.nl/~hanwen
___
lilypond-devel mailing list
lilypond-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-devel
patch for scm/editor.scm to add KDE (Kate) support.
Please find attached a patch that adds support for kate (KDE's editor) to
lilypond-invoke-editor . (Kate: http://kate-editor.org/)
Kate numbers lines starting with 0, so I had to add some code to decrease the
line number in the textedit:// url by one. The special string %(line-1)s is
replaced with the line number minus one.
with best regards,
Wilbert Berendsen
--
http://www.wilbertberendsen.nl/
"You must be the change you wish to see in the world."
-- Mahatma Gandi
--- scm/editor.scm 2007-09-19 14:50:18.0 +0200
+++ /home/wilbert/Desktop/editor.scm 2008-01-30 08:01:55.0 +0100
@@ -8,6 +8,7 @@
;; Also for standalone use, so cannot include any lily modules.
(use-modules
+ (ice-9 format)
(ice-9 regex)
(srfi srfi-13)
(srfi srfi-14))
@@ -37,6 +38,7 @@
("gedit" . "gedit +%(line)s %(file)s")
("jedit" . "jedit -reuseview %(file)s +line:%(line)s")
("syn" . "syn -line %(line)s -col %(char)s %(file)s")
+("kate" . "kate --use --line %(line-1)s --column %(column)s %(file)s")
("lilypad" . "lilypad +%(line)s:%(char)s %(file)s")))
(define (get-command-template alist editor)
@@ -66,8 +68,9 @@
(command
(re-sub "%\\(file\\)s" (format #f "~S" file-name)
(re-sub "%\\(line\\)s" (format #f "~a" line)
- (re-sub "%\\(char\\)s" (format #f "~a" char)
- (re-sub
- "%\\(column\\)s" (format #f "~a" column)
- (slashify template)))
+ (re-sub "%\\(line-1\\)s" (format #f "~d" (- (string->number line) 1))
+ (re-sub "%\\(char\\)s" (format #f "~a" char)
+ (re-sub
+ "%\\(column\\)s" (format #f "~a" column)
+ (slashify template
command))
___
lilypond-devel mailing list
lilypond-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: Chord fonts
Hmmm, strange. I've done a "make distclean" and a "make web", but the "m" and "s" are still chosen from the wrong font. I'll try to investigate it later today. Can anyone else reproduce this, or am I the only one with this problem? Erlend On 30. jan. 2008, at 07:19, Werner LEMBERG wrote: The chord font seems to be messed up after the mf2pt1 change. The letter "m" and "s" is chosen from the dynamic font (see attached picture). Can you reproduce this? No, I can't repeat with the current git. For me, the chord name chard from the lilypond manual's appendix just displays fine (using ArialMT installed on GNU/Linux box). Werner ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
calling lilypond-book on the IR
Would it be possible to run the IR through lilypond-book? I recently tried adding a @lilypond[] example to something in scm/ but it didn't work. I'm just asking how hard this would be; this isn't an official request. Not yet, anyway... :) Cheers, - Graham ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: \times -> \tuplet (was Re: Issue 566 in lilypond: showStaffSwitch -> \staffSwitchOn)
2008/1/30, John Mandereau <[EMAIL PROTECTED]>: > See Guile docs; there may be installed in Info format on your GNU/Linux > system. I'm not a Scheme specialist, but I think you should generally > consider RxRS as a standard specification, and always look at Guile docs > to look for additional features. Oh yes, great idea! If only I had the chance to be running Linux... :-( I'll have a look into it. Thanks, Valentin ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: \times -> \tuplet (was Re: Issue 566 in lilypond: showStaffSwitch -> \staffSwitchOn)
Le mercredi 30 janvier 2008 à 10:32 +0100, Valentin Villenave a écrit : > Wow, that's interesting! I have been browsing the whole R6RS > specification to see if Scheme could accept fractions as arguments, > but I couldn't come up with anything... See Guile docs; there may be installed in Info format on your GNU/Linux system. I'm not a Scheme specialist, but I think you should generally consider RxRS as a standard specification, and always look at Guile docs to look for additional features. Cheers, John ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: \times -> \tuplet (was Re: Issue 566 in lilypond: showStaffSwitch -> \staffSwitchOn)
2008/1/30, Han-Wen Nienhuys <[EMAIL PROTECTED]>: > it's actually possible to have > > \func #2/3 > > but you would loose the difference between 4/6 and 2/3 Wow, that's interesting! I have been browsing the whole R6RS specification to see if Scheme could accept fractions as arguments, but I couldn't come up with anything... Anyway, the use of a hash character just makes it even more annoying than \times, \tuplet or whatever. I'd definitely vote for tuplet (or, in a more extreme way, my minimalistic \t approach :-) Cheers, Valentin ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: replacing Century Schoolbook font
Han-Wen Nienhuys schrieb: 2008/1/28, Werner LEMBERG <[EMAIL PROTECTED]>: You can insert any UTF-8 character and LilyPond will render it as long as Pango can find a font installed on your system that includes a glyph for that symbol. Pango also handles kerning and ligatures automatically, if the font(s) you use provide enough information and glyphs (for example, Century Schoolbook shipped with LilyPond include ligatures glyphs such as "fl", whereas Liberation fonts don't, at least not "fl" I tested with "flûte"), [...] Well, Till doesn't mean this. He talks about OpenType features like `smallcaps'. I have no idea about this. You'd have to ask on the pango list, and port their suggestions to pango-font.cc. Yes I had already the impression that this is totally handled by pango. I thought of something like when calling the font that you could add the openfont features, like +onum and the like. Till ___ 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
Re: Chord fonts
> The chord font seems to be messed up after the mf2pt1 change. The > letter "m" and "s" is chosen from the dynamic font (see attached > picture). Can you reproduce this? No, I can't repeat with the current git. For me, the chord name chard from the lilypond manual's appendix just displays fine (using ArialMT installed on GNU/Linux box). Werner ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
