Re: Title font changed?
Hi Jean, Thanks for notifying me. I can confirm that the fix solves the problem. I was able to typeset a score with the right fonts after re-running brew install lilypond. Thanks a lot for fixing this! Best, Bart > Op 18 jan. 2023, om 16:54 heeft Jean Abou Samra het > volgende geschreven: > > > > Le 14/01/2023 à 10:30, Bart Kummel a écrit : >> Hi Jean, >> >> Thanks for your reply. Very insightful! I wonder why Google didn’t come up >> with a link to this issue… >> >> Anyway, it looks like the solution will be merged into Homebrew’s main soon. >> I might be able to just wait for it. I’ll keep an eye on the issue. >> > > > Should be fixed now. Can you confirm that it works after upgrading the > lilypond formula? > > Best, > Jean >
Re: Title font changed?
As a follow up, I can confirm that installing the fonts manually from https://github.com/ArtifexSoftware/urw-base35-fonts also fixed the problem. Can be a work around if you want to stick with the Homebrew installation. > Op 14 jan. 2023, om 10:30 heeft Bart Kummel het volgende > geschreven: > > Hi Jean, > > Thanks for your reply. Very insightful! I wonder why Google didn’t come up > with a link to this issue… > > Anyway, it looks like the solution will be merged into Homebrew’s main soon. > I might be able to just wait for it. I’ll keep an eye on the issue. > > Thanks again! > > Best, > Bart > >> Op 13 jan. 2023 om 21:04 heeft Jean Abou Samra het >> volgende geschreven: >> >> >> >> >>> Le 13 janv. 2023 à 20:19, b...@kummelweb.nl a écrit : >>> >>> Hi, >>> >>> Since I upgraded tot Lilypond 2.24, I noticed that the title font changed. >>> It looks much more like standard Times New Roman now, instead of the >>> beautiful Lilypond text font. (See the attached images: old.png is how it >>> used to be, new.png is after upgrading to 2.24.) >>> >>> I can't find anything about a change of the text font in the CHANGED page, >>> so I figure there should be something wrong with my install. >> >> >> Yes, there is. It’s a bug in Homebrew. See >> https://github.com/Homebrew/homebrew-core/issues/119476 >> >> Please use the binaries from lilypond.org until this is fixed. >> >> Best, >> Jean >>
Re: Title font changed?
Hi Jean, Thanks for your reply. Very insightful! I wonder why Google didn’t come up with a link to this issue… Anyway, it looks like the solution will be merged into Homebrew’s main soon. I might be able to just wait for it. I’ll keep an eye on the issue. Thanks again! Best, Bart > Op 13 jan. 2023 om 21:04 heeft Jean Abou Samra het > volgende geschreven: > > > > >>> Le 13 janv. 2023 à 20:19, b...@kummelweb.nl a écrit : >>> >> Hi, >> >> Since I upgraded tot Lilypond 2.24, I noticed that the title font changed. >> It looks much more like standard Times New Roman now, instead of the >> beautiful Lilypond text font. (See the attached images: old.png is how it >> used to be, new.png is after upgrading to 2.24.) >> >> I can't find anything about a change of the text font in the CHANGED page, >> so I figure there should be something wrong with my install. > > > Yes, there is. It’s a bug in Homebrew. See > https://github.com/Homebrew/homebrew-core/issues/119476 > > Please use the binaries from lilypond.org until this is fixed. > > Best, > Jean >
Re: producing archival scores
Hi List, I just read this very interesting discussion. I don't think this is a problem that will easily be solved. In fact, this is not a Lilypond- or even music notation-specific problem. Similar cases exist for all other file formats. (For example: how future proof is Microsoft's .doc format?) However, I just want to add another possible direction for a solution. I recently came across a project called XSugar (www.brics.dk/xsugar/). It's a tool that gives the possibility to transform between XML and non-XML formats in two directions. (Unlike XSLT, which can do a transformation from XML to non-XML, but not the other way around.) I think it should be possible to write a XSugar grammar for converting Lilypond format to MusicXML and back. Unfortunately I don't have the time to investigate this, but perhaps someone else has... Best regards, Bart Kummel, Hilversum, The Netherlands On 4/12/07, Valentin Villenave [EMAIL PROTECTED] wrote: 2007/4/12, Stuart Pullinger [EMAIL PROTECTED]: In conclusion: SVG provide an alternative to PDF which may be more future-proof provided that you are prepared for patchy support in current browsers. ...and provided that multi-pages SVG support is not yet really available, which makes it rather unsuitable for musical purposes (as you may know it, most of scores tend to make more than one page ;-) ...though it would indeed be a very good idea to design some special music-oriented SVG-like vector graphics format. (PS. Thank you so much Cameron for the link: I didn't knew about this interview but it's been a pleasure to discover it; I perfectly agree with Jan and Han-Wen about all of it, particularly their vision of MusicXML weakness and superficiality.) Regards, Valentin Villenave. ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Re:A new freeware LilyPond editor for Windows (Thibaut Chevalier)
Hi Anders,I think you should tell conText to use Unicode. This can be done via the menu Options Environment options... Editor. Under Default settings for a new document set File format to Unicode. Existing files can be converted with Tools Convert Text To... Unicode. Good luck! Best regards,Bart Kummel, Hilversum, The NetherlandsOn 7/27/06, anders stenberg [EMAIL PROTECTED] wrote:Hi!Did download install the conText editor Your highlights difine the user-keys sugested.I like the editor (have been working on jEditwhich is slow sometimes) .One problem: as a native swedish speaker i need the skands ie. å,ä,ö.which work when runing Lilypondin conText ifyou enter not the charachters but weirdoes like Ã¥ . If I enter the char from keyboardIgett a blank . So I am not quite convinced of the conText as yet.Anders Stenberg___lilypond-user mailing list lilypond-user@gnu.orghttp://lists.gnu.org/mailman/listinfo/lilypond-user ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Even and odd page-margins
Hi all,Is there some progress in this area? I'm still willing to co-sponsor the even/odd margin feature for EUR 15,00. Perhaps is can be combined with the feature for page layout sections?Best regards,Bart Kummel, Hilversum, The Netherlands On 5/27/06, Bart Kummel [EMAIL PROTECTED] wrote: Hi Han-Wen, Gianluca,I don't know if anybody else is going to help sponsoring the mirrored-margins feature, but you can add me to the list for EUR 15.Best regards,Bart Kummel, Hilversum, The Netherlands On 5/26/06, Han-Wen Nienhuys [EMAIL PROTECTED] wrote: Gianluca D. schreef: Hi everybody! I'd like to ask if anyone knows a way to set different margins for odd and even pages with Lilypond. I've tried to find some information from the manual of boh 2.8 and 2.9 version, but I couldn't find anything. I wouldn't like to use lilypond-book to achieve my goal, because I think it would be a waste of resources to use two different programs to obtain a simple thing like this. I'd be also interested in sponsoring this feature, eventually.Hello!I can add this for 65 EUR. Another feature I'd like to see in lilypond is a set of properties for the first page of a score, or the page with title- something like first-page-between-system-space or first-page-top-margin; actually, the first page usually needs specific tuning, which are often not suitable for the rest of the score- so I've thought it would be pretty nice to have specific settings for the title-page. I would be interested in sponsoring this feature too.I can add code to override all relevant page dimensions for the firstpage only, for 130 EUR. Cheers,--Han-Wen Nienhuys - [EMAIL PROTECTED] - http://www.xs4all.nl/~hanwenLilyPond Software Design -- Code for Music Notationhttp://www.lilypond-design.com___ lilypond-user mailing list lilypond-user@gnu.orghttp://lists.gnu.org/mailman/listinfo/lilypond-user ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Even and odd page-margins
Hi Han-Wen, Gianluca,I don't know if anybody else is going to help sponsoring the mirrored-margins feature, but you can add me to the list for EUR 15.Best regards,Bart Kummel, Hilversum, The Netherlands On 5/26/06, Han-Wen Nienhuys [EMAIL PROTECTED] wrote: Gianluca D. schreef: Hi everybody! I'd like to ask if anyone knows a way to set different margins for odd and even pages with Lilypond. I've tried to find some information from the manual of boh 2.8 and 2.9 version, but I couldn't find anything. I wouldn't like to use lilypond-book to achieve my goal, because I think it would be a waste of resources to use two different programs to obtain a simple thing like this. I'd be also interested in sponsoring this feature, eventually.Hello!I can add this for 65 EUR. Another feature I'd like to see in lilypond is a set of properties for the first page of a score, or the page with title- something like first-page-between-system-space or first-page-top-margin; actually, the first page usually needs specific tuning, which are often not suitable for the rest of the score- so I've thought it would be pretty nice to have specific settings for the title-page. I would be interested in sponsoring this feature too.I can add code to override all relevant page dimensions for the firstpage only, for 130 EUR. Cheers,--Han-Wen Nienhuys - [EMAIL PROTECTED] - http://www.xs4all.nl/~hanwenLilyPond Software Design -- Code for Music Notationhttp://www.lilypond-design.com___lilypond-user mailing list lilypond-user@gnu.orghttp://lists.gnu.org/mailman/listinfo/lilypond-user ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Helping with the documentation
Hi all,Unfortunately I do not agree with most of your points. About searching: I often use google. With the option site:lilypond.org you can narrow the search to that site and by including a version number in the search terms you can narrow it down to one version. This method could be used with a wiki too. About the tarballs. Most Windows users don't even know what a tarball is. Personally I hate local documentation. I always have a browser window open, so it's very easy to seach for a topic by using Google as explained above. And Graham: I don't get your point saying that the current docs are easier to maintain that a wiki. In the current setup, every piece of documentation has to go through your hands. With a wiki, everyone could add things themselves, so you will get far less work, even if you think editing a wiki is more comples than what you are doing now. (Apart from the fact that in my opinion there is nothing simpler than editing a wiki page...) Making tarballs available with newer docs than the website looks like a good step, but I think a website should always represent the latest state. One of the reasons that earlier wiki's weren't a big success could be that people do not want another place to look for documentation. Therefore the best solution (in my opinion) is to replace the current docs with a wiki. I think the way the documentation is done now is a little bit oldfashioned. It may be good for the linux-geeks amongst the lilypond users. But for Windows users, who generally have less knowledge about operating systems, it is now not easy to use and/or to contribute. Let me end with this: I do appreciate all the work you do in making both lilypond itself and its documentation better with every release. You're all doing a great job! Thanks for that! Best regards,Bart Kummel, Hilversum, The NetherlandsOn 4/14/06, Graham Percival [EMAIL PROTECTED] wrote:On 14-Apr-06, at 8:20 AM, Bart Kummel wrote: So I was thinking of a method to make contibuting to the docs more easy. Perhaps it's a good idea to set up a wiki for the docs.As other people have pointed out, we've tried wikis in the past.Thelatest version is still online: http://wikihost.org/wikis/lilypond/In addition, adding new material to the docs is EASIER than using awiki. I think there are many benefits for using a wiki instead of the way the documentation is done now. I think it's more easy for the editor, because he doesn't have to add all contibutions manually,This is absolutely NO problem for me if I get an email which proposesthe exact changes.The problem in writing docs is in coming up withthe initial text, not in the technical step of translating it into texinfo. Another benefit is that we don't have to wait until a new version of Lilypond is built for new documentation to come available on-line.If this is a serious concern, I could start making doc tarballs available -- or even hosting temporary docs on my webpage.I agreethat sometimes this has bothered me.A third benefit is that the documentation does not depend on one or a few persons any more. There is nothing intrinsic in a wiki that does this.Whether thedocumentation depends on a few people is simply a matter of thecommunity.As I've said, adding new material to the docs is easierthan adding an entry to a wiki.All you need is email. Cheers,- Graham ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Helping with the documentation
I think you're missing at least part of my point. I know how to useGoogle with a targeted search. The problem is that the amount of text surrounding a match that Google returns is often insufficient todetermine if it's what I want, whereas scanning through the wholemanual in a browser automatically returns an entire page of context(if I want it). OK, Got the point now. Personally I hate local documentation. Many people don't have reliable broadband always available.You have told us about your personal preferences, which is entirelylegitimate. But my personal preferences are that I really, reallydon't like using wiki-only documentation. This discussion is not only about personal taste. It's about the fact that a large part of the people who maintain lilypond and its documentation are people who are very familiar with computers, linux, et cetera. I'm trying to act as a devil's advocate here: there are lots of people out there using Windows, having not much computer knowledge, who are potential users of and contributors to lilypond + docs. I think we're missing those people here, because we do things in a linux-like way. Using a wiki is just one suggestion to change this. Perhaps there are other ways. I'd like to hear other people's ideas about this.Best regards,Bart Kummel ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Helping with the documentation
Hi Graham,What I'm missing currently in the docs is a section about organ music. There are some instrument-specific things that can be discussed in such a section. I'm willing to help with that, but I have very little spare time. So I was thinking of a method to make contibuting to the docs more easy. Perhaps it's a good idea to set up a wiki for the docs. I believe there is a lilypond plugin for wikis, to make it easy to post comments and their results. We could start by only adding some new topics and then gradually move more and more topics from the old docs to the wiki. After some time we end up with the full documentation in a wiki. Since wikis have a versioning system built in, we could use that to keep info for older versions of Lily available. I think there are many benefits for using a wiki instead of the way the documentation is done now. I think it's more easy for the editor, because he doesn't have to add all contibutions manually, he only has to edit them. Another benefit is that we don't have to wait until a new version of Lilypond is built for new documentation to come available on-line. A third benefit is that the documentation does not depend on one or a few persons any more. I hope you want to consider my suggestions. As I said, I don't have much time, but I'm willing to help in the few moments I have. I have some experience with setting up a wiki. And for the documentation itself: I play the organ as an amateur, so I know a low about organ and also choral music notation. Best regards,Bart Kummel, Hilversum, The NetherlandsOn 4/14/06, Graham Percival [EMAIL PROTECTED] wrote:Hi all,I'm getting a bit overwhelmed working on the documentation, so I'm asking for help.I've posted a list of tasks to the -devel mailist.Some of them require very little previous knowledge of LilyPond, andare actually a great way to learn.You can read them here: http://lists.gnu.org/archive/html/lilypond-devel/2006-04/msg00231.htmlApart from those tasks, I have on more request: please don't forward anemail from -user to -devel or the bug mailist with the message you should improve the docs in this area.If you think an email containsimportant information or clarification of the documentation, pleasetake the time to propose *exact* changes to the documentation.If you are personally involved in the discussion, then you probably know moreabout this area than I do.This is certainly true if the issueinvolves anything that is covered in Chapter 7 Instrument-specificnotation. Finally, some background about me: I'm just a normal user.In August2004, I volunteered to become Documentation Editor, because I speakEnglish as a first language and have some time to contribute.I didn't program LilyPond, nor do I have any special training in musicpublication.I play cello and viola at a high level (as a universityundergraduate performer); my knowledge about printed music comes fromreading music.I have seen a lot of string music, and some orchestral scores, but I have very little knowledge of vocal music, piano, guitar,and the like.If you play any of those instruments -- anything whichis in Chapter 7 -- then I practically guarantee that you know more about using LilyPond to create music for those instruments.For information about proposing changes to the docs, seehttp://lilypond.org/web/devel/participating/documentation-adding Thanks,- Graham___lilypond-user mailing listlilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: [Fwd: Re: The organ template works fine now but ....]
I think you should do this in a seperate layout block, likt this:\version 2.8.0\new StaffGroup \with{systemStartDelimiter = #'SystemStartBar } \new PianoStaff \new Staff \relative c' {c d e f }
\new Staff \relative c' {\clef bass c b a g } \new Staff \relative c { \clef bass c1 }\layout { \context { \Staff \override VerticalAxisGroup #'minimum-Y-extent = #'(-6 . 6)
}}Hope this helps.Best regards,Bart Kummel, Hilversum, The NetherlandsOn 4/9/06, MX
[EMAIL PROTECTED] wrote:-- Forwarded message --
From: MX [EMAIL PROTECTED]To: Mats Bengtsson [EMAIL PROTECTED],
[EMAIL PROTECTED]Date: Sun, 09 Apr 2006 08:09:23 +0200Subject: Re: The organ template works fine now but Yhank you for youranswers !The new scheme you proposed is OK.But I tried to tune interval between pedal stave et piano staves with:
* \override Staff.VerticalAxisGroup #'minimum-Y-extent = #'(-1 . 1)*with no result. It changes extent between the groups of three staves butnon between the peadal stave and piano staves.I varied the value (-1 . 1) with no result, I changes position of the
command \override. Wherehave I to place the command \override etc.\new StaffGroup \with{systemStartDelimiter = #'SystemStartBar } *here ?* \new PianoStaff *here ?* \new Staff \relative c' {c d e f }
\new Staff \relative c' {\clef bass c b a g } *here ?* \new Staff \relative c {\clef bass c1 } The syntax of the commands in general is confused and not completelydocumented.
Thank you.GGLe 08.04.2006 20:19,: I don't think that helps, since PianoStaff sets a fixed spacing between its staves. I would recommend the following solution, which in a
way is easier than what I initially proposed, namely to use a PianoStaff only for the manual staves and enclose all three staves in a GrandStaff. The only trick that's needed then is to get rid of the bracket, which is easy:
\new StaffGroup \with{systemStartDelimiter = #'SystemStartBar } \new PianoStaff \new Staff \relative c' {c d e f }\new Staff \relative c' {\clef bass c b a g }
\new Staff \relative c {\clef bass c1 } Now, you can change the minimum y extent of the pedal stave separately, if needed. /Mats
Trevor Bača wrote: have you tried minimum y extent? On 4/6/06, MX [EMAIL PROTECTED] wrote:
-- Forwarded message -- From: MX [EMAIL PROTECTED] To: Mats Bengtsson
[EMAIL PROTECTED] Date: Thu, 06 Apr 2006 22:36:02 +0200 Subject: The organ template works fine now but ... Thank you very much Mats, it works fine now.
If someone asked you how to tune the distance between the pedal staff and the manuale staves, what would you answer ?I know someone who tried very hard with overrideProperty commands, VerticalAlignment etc.
and who did not manage to do anything... M.X. Le 05.04.2006 20:09,: Simple, just replace StaffGroup by PianoStaff.
/Mats GG wrote: Unfortunately, it seems that this solution doesn't authorize the
staff changes between the manuale staves, as in the Pianostaff command. M.X.
___ lilypond-user mailing list
lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
-- Trevor Bača [EMAIL PROTECTED]
___ lilypond-user mailing list
lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user___
lilypond-user mailing listlilypond-user@gnu.orghttp://lists.gnu.org/mailman/listinfo/lilypond-user
___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user
Include date?
Hello list! I'm using Lilypond 2.8.0 on windows XP. For versioning reasons, I would like to automatically include the date the PDF is generated in one of the title fields. I was thinking of a hack like this one: #(string-append subsubtitle LilyPond version (lilypond-version)) I tried a lot of possibilities, like: #(string-append Generated on: (date)) But I cannot find the right variable name to use instead of date. Does anyone know a variable name that works for this purpose? Or does it not exist? (I suppose this has to be part of the Scheme language, but I'm not very familiar with that.) Best regards, Bart Kummel, Hilversum, The Netherlands. ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: PDF size
Hi!I'm also suffering from huge PDF files. Turning off point-and-click does help just a little bit. I saw the source code patch for Ghostscript on lilypond-bug, but unfortunately I'm not able to recompile my own Ghostscript. Is there some patched binary available somewhere? I'm on Windows XP. (Using lily 2.8.0). Best regards,Bart Kummel, Hilversum, The Netherlands.On 4/5/06, Mats Bengtsson [EMAIL PROTECTED] wrote:Harald Wellmann wrote: I hope you have seen the related emails on the mailing list. I've seen some, but none that really solved my problem. That's why I posted my question. Unless you have a specific link to a thread, a reference to related emails does not really help... I should have hinted you to also search the archives ofbug-lilypond. For example, you will find:http://lists.gnu.org/archive/html/bug-lilypond/2006-03/msg00296.html which tells that the culprit is Ghostscript and how tofix it (if you're prepared to recompile Ghostscript). /Mats___lilypond-user mailing list lilypond-user@gnu.orghttp://lists.gnu.org/mailman/listinfo/lilypond-user ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Include date?
Thanks a lot! This simply works. And it's flexible too, since I can manipulate the %d-%m-%Y string!Bart KummelOn 4/5/06, Toine Schreurs [EMAIL PROTECTED] wrote: Try:date = #(strftime %d-%m-%Y (localtime (current-time)))Toine Schreurs I'm using Lilypond 2.8.0 on windows XP. For versioning reasons, I would like to automatically include the date the PDF is generated in one of the title fields. I was thinking of a hack like this one: #(string-append subsubtitle LilyPond version (lilypond-version)) I tried a lot of possibilities, like: #(string-append Generated on: (date)) ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Mirror margins
I think I'm going to give lilypond-book a try, as Graham suggested. (Thanks for that Gramah!) I hope to find some time this weekend. Has someone already done this with lilypond-book? Please let me know your experiences and perhaps someone can be so kind to share some example with the mailinglist... To Geoff: Thanks for the suggestion, but a hardware solution was not what I was looking for. Personaly I hate those sheet protectors, because you always suffer from reflections and you cannot write directly on the music. (Oh, and by the way: in Europe we use A4 and most A4-binders have either 2, 4 or 23 rings...) And for protecting my pages for tearing loose, I use little stickers with a hole, which are made for this purpose. Regards,Bart KummelOn 3/22/06, Geoff Horton [EMAIL PROTECTED] wrote: My question is about the margins. My songbook consists of a D-ring binder, so I need some space where I can punch the holes. I can only find settings for left and right margins, but as you probably know, the holes are on the right on even pages and on the left on odd pages. So I need the margins to be mirrored on even and ood pages.For a hardware solution, try putting the sheets into transparentthree-hole sheet protectors. As an added bonus, it will be a lot harder for them to tear loose by accident.Geoff-- Bart en Joke KummelKarel Doormanlaan 1461215 NR Hilversum tel.: (035) 6 235 215fax: (087) 78 46 768e-mail Bart: [EMAIL PROTECTED]e-mail Joke: [EMAIL PROTECTED]e-mail samen: [EMAIL PROTECTED]website: www.kummelweb.nl ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Mirror margins
Hi gmane.comp.gnu.lilypond.general, I am using Lilypond quite often and I like it very much! Most of the time I use Lilypond to extend and/or adapt my church songbook. Recently I began to create a sort of template to make the Lilypond look more like the original music in the songbook. Think of things like selecting another font for titles, moving the page numbers to the footer, etc. My question is about the margins. My songbook consists of a D-ring binder, so I need some space where I can punch the holes. I can only find settings for left and right margins, but as you probably know, the holes are on the right on even pages and on the left on odd pages. So I need the margins to be mirrored on even and ood pages. I tried to write some Scheme code to achieve this, but since I'm not very familiar with Scheme, I did not succeed. Is it possible to get mirrored margins by means of some hack? Has somebody done this before? (I already searched the snippet repository.) I am a programmer, so I'm not affraid of some hacking around, but Scheme is not a language I'm familiar with, so I'd appreciate need some help on that. Best regards, Bart Kummel, Hilversum, The Netherlands ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
