more stupid questions
[EMAIL PROTECTED] writes: > This is all using 1.6.9. I must admit it either I simply don't get it or > chords are quite broken in 1.6.9. You got it right. > Is this better in more current > versions? Try a recent 1.7 release. -- Han-Wen Nienhuys | [EMAIL PROTECTED] | http://www.xs4all.nl/~hanwen ___ Lilypond-user mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/lilypond-user
Re: more stupid questions
Atte André Jensen wrote: 2) I'd like to be able to have the bassnote printed in lowercase instead of uppercase. Possible? If so is it a question of hacking chord-name.scm? 3) I'm Danish. In this strange country we write "H" when everybody else writes "B". So how do I get "B" in chordnames? Take a look at input/test/chord-names-german.ly in latest cvs (1.7.20.something). I am sorry, but I am afraid that you will have to compile for yourself. 5) I get some warning: can't find ascii character: 248 warning: can't find ascii character: 229 warning: can't find ascii character: 248 warning: can't find ascii character: 248 warning: can't find ascii character: 248 warning: can't find ascii character: 229 warning: can't find ascii character: 248 warning: can't find ascii character: 230 warning: can't find ascii character: 230 Is this caused by me using æ (ae), ø (slashed o), å (circle over a) and ü (two dots over u)? The output looks fine in xdvi, should I simply ignore the warnings? This is a known and afaik unsolved problem. The letters are correct, but the spacing gets messed up. :-( -Rune ___ Lilypond-user mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/lilypond-user
Re: more stupid questions
5) I get some warning: can't find ascii character: 248 warning: can't find ascii character: 229 warning: can't find ascii character: 248 warning: can't find ascii character: 248 warning: can't find ascii character: 248 warning: can't find ascii character: 229 warning: can't find ascii character: 248 warning: can't find ascii character: 230 warning: can't find ascii character: 230 Is this caused by me using æ (ae), ø (slashed o), å (circle over a) and ü (two dots over u)? The output looks fine in xdvi, should I simply ignore the warnings? This is a known and afaik unsolved problem. The letters are correct, but the spacing gets messed up. :-( Did you try \property Lyrics.LyricText \override #'font-name = #"ecrm1000" (assuming that the question was about lyrics, you can do similar settings for text scripts, for example) /Mats ___ Lilypond-user mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/lilypond-user
Octave transposer for editing
Several users have asked for this over the years, so here it is, an octave transposer editing tool: http://www.openguitar.com/files/octly.txt -- The biggest losers of all are the winners of an unjust war. The wars are not over. Just the winning part is over. Bush lied. Thousands died. dra@ http://www.openguitar.com ___ Lilypond-user mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/lilypond-user
hallo
Hallo! Hab eine neue Seite im web entdeckt. Kannst ne Menge Spaß haben oder selbst verdienen! www.sexcamdreams.de Bussi Janina ___ Lilypond-user mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/lilypond-user
New Arena Product For Operators
Hockey Arena Product As Important As The Ice EdgerClick To Learn More & See Product Movie Product announcements, arena industry news, safety alerts, and free promotional activities provided by[EMAIL PROTECTED] you would like to be removed for the Arena-Watch mailinglist, simply type remove in the subject line and return. ___ Lilypond-user mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/lilypond-user
unable to launch Lilypond
GNU LilyPond 1.6.6ERROR: In procedure primitive-load-path: ERROR: Unable to find file "ice-9/boot-9.scm" in load path This is the message I receive after I type in /sw/bin/lilypond using terminal on OS X (10.2.3). I'm a complete unix newbie using FinkCommander to install unix apps. I've had success installing and launching The Gimp in the previously mentioned manner. When FinkCommander had finished installing Lilypond, I got the following message - Installation Complete. @@@ Start a new shell to get the correct lilypond environment settings. * GNU LilyPond: (lilypond).The GNU music typesetter. install-info(/sw/share/info/lilypond.info): no section specified for new entry, placing at end * GNU LilyPond internals: (lilypond-internals). LilyPond internals. install-info(/sw/share/info/lilypond-internals.info): creating new section `GNU music project' Do you have any suggestions or solutions that will get me up and running Lilypond? I thank you for your time and patience with a unix newbie. Roy Schienmann ___ Lilypond-user mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/lilypond-user
lilypond 1.6.10 on Slackware 9.0 done.
It is currently working quite alright on my box (almost stock Slackware 9.0, except the kernel), so I thought I'll write to add to the documentation. It is gcc 3.2.2, BTW, so the info might be useful to other systems. Firstly, I need these packages to build lilypond plus docs (in addition to what's on the slackware 9.0 CD). Slackware 9 ships flex 2.5.4a, which doesn't work with gcc 3.2.2 regarding lilypond. (upgrading flex works, while neither of the gcc 3.0.x and gcc3.1.x tips regarding flex 2.5.4a work for gcc 3.2.2). t1utils-1.27-1Fri Jun 6 19:48:18 2003 flex-2.5.31-0 Fri Jun 6 14:20:23 2003 autotrace-0.30-1 Fri Jun 6 14:16:59 2003 mftrace-1.0.17-1 Fri Jun 6 14:14:13 2003 pfaedit-030518-1 Fri Jun 6 04:57:57 2003 (I wish the readme/install file is more clear about the requirements) I tried rpm -bb lilypond-x.y.z/make/out/lilypond.redhat.spec with both 1.6.10 and 1.7.20, but it bombed out during generation of lilypond.dvi. Turn out Slackware 9 has a similar problem regarding TeX's memory usage as debian. Only extra_mem_top and extra_mem_bot needs changing - pool_size is 125, much larger than lilypond needs. Then I found that the generated lilypond.pdf is broken. (funny rhombus shape where the notes should be). Turned out there is a lot of problem with the dvips -ulilypond.map -Ppdf lilypond.dvi . First, it doesn't work (pdf broken). Second, it leaves behind stale pk files in /var/cache which breaks dvips lilypond.dvi (without any options), or indeed any dvi file using the feta fonts. Something to do with trying to generate pk files at 8000dpi without success, and back down to 600dpi, dumping pk fonts in /var/cache. Anyway, here is what works: (1) remove the stale pk files under /var/cache/fonts (2) use dvips -ulilypond.map -Poutline lilypond.dvi (or -Pcmz). -Ppdf is definitely bad. This is as much as I remember. (it took a long time and a lot of trial and error to fix everything). But yes, the quality is good as typical of TeX-derived systems. ___ Lilypond-user mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/lilypond-user
