Re: make web fails for LilyPond 2.8.0/2.9.0 source drop [Also] Re: Futile attempts to build LilyPond 2.8.0
On Tuesday 04 April 2006 10:47, Andreas Scherer wrote: > R. Mattes mh-freiburg.de> writes: > > Ok, i found the "bug". It looks like this is triggered > > by using guile-1.6.n instead of guile-1.8 - this also > > explains why Andreas' build failed. > > Confirmed. After updating OpenSUSE 10.0 with guile-1.8.0, all is well > again. "make all web" runs to completion with both the LilyPond 2.8.1 > source drop and the 2.9.1 CVS contents. > I encountered the same error, But it is not a bug in itself; just that the configure tests against old versions of certain programs, guile and mftrace that i know about. Maybe an action for the main-core developers to update the files which contain old info, so an end-user who is familiar with the normal build-procedure can use it. The GUB-option is nice, but has also some restrictions build in, and is not completely user-friendly when you are updating an older version. If I know what to change, I will try to update the CVS for the new versions (2.[89].X). Greetings, Herman Grootaers ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
Mandriva 2006 install now OK
Ladies, gentlemen, I finally got the problem of a source-install of lilypond fixed. It was the ./configure which put me on a very wrong track. Mandriva 2006 installs standard mftrace 1.1.16 in /usr/bin, but lilypond requires mftrace 1.1.19 to get the fonts running. Downloading the mftrace-tar-ball from Han-Wen's website, (http://www.xs4all.nl/~hanwen/mftrace/) installing it and renaming/deleting the old mftrace and gf2pbm together with a new install of the lilypond-tarball gave me a good compile / install. Finally I can run Lilypond as I am used to, from the sources, although the GUB-distribution is a good replacement. Thanks everybody for a good typesetting-program, and now up to setting the scores of two choirs, in cyrrilic for the church-choir and for my other group, which is folk-style based. Greetings, Herman Grootaers ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
Fonts are not generated in 2.7.[30-36]
Ladies, gentlemen, I am currently trying to build Lilypond om my machine ( Mandriva 2006 powerpack, 1024 MB memory, AMD64 / 3500+ ), but it fails in the mentioned series 30-36. The problem, as I can tell/see, is that fontforge fails after reading the first 149 characters while processing emmentaler11.pe. I have traced back to the source, but as I cannot be sure what goes on where, it seems to me that gf2pbm seems to generate the problem. I have taken a look at the pamesan11.pfa and the feta11.pfa files with fontforge, but they appear to be empty, no characters appear in the screen. As emmentaler*.pfa is a merge of feta*.pfa and parmesan*.pfa, can that explain why fontforge dumps when generating the emmenthaler*.pfa. I have reported this already in January on the developer-mailing-list, but I have got no answer then; but as we are now going for a new release I think this becomes instaed of a irritation an real problem. Also, I am not able to retrieve the generated fonts from the shortcuts which are to be found in the make-file/INSTALL-guide. However, on the mandriva distrolist is an RPM for emmentalerfonts named ec-fonts-mftraced-1.0.9-1mdk, but this one is for Lilypond 2.6.3. There are several places where you can download this RPM, so that could be a possible shortcut, if the fonts are not changed between the versions. On the other hand I have worked with the GUB-distro, which works fine, so there could also be a possibility to get the fonts from. This brings me to the following question: - when the new release is out will the GUB-distro also contain lilypond-book and convert-ly for the Linux-distro? Also a very minor detail , in the Doxyfile in the tree is still the old version (2.5) mentioned. Greetings, Herman Grootaers ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: [OT] How do you configure your keyboard for programming?
On Sunday 29 January 2006 23:46, Pedro Kröger wrote: > Sorry for the off-topic, but I'm curious about this. Since a few > people here speak languages other than English (french, German, > Dutch, Portuguese, etc) I was wandering how you configure your > keyboard for *programming*. > > The use of dead keys is very comfortable to edit texts in languages > with accents (like french) but I find a little bit irritating to use > it while programming because I always have to hit a few more keys. > For instance, to type an expression in lisp that have a quote I have > to type foo to get 'foo instead of foo. > that's even more annoying to type commands like C-c ` in emacs. > > So, what do you do: > > 1. just use the keyboard with deadkeys, type the extra keys and not > care much > > 2. don't use deadkeys (but how do you write accents in your > language?) > > 3. switch keyboard maps > > 4. do something else > > Any ideas? > I did default my keyboard to US-layout, just because the dead-keys are too cumbersome to use and not realy necessary in dutch. For Russian I switch my keyboard-layout to a modified russian keyboard, because the mapping is not as the keys indicate. Maybe I will get the dutch keyboard also switched, but that depends on what my requirements are on that moment. == Herman Grootaers ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: lilypond-book broken in GUB 2.7.27-4
On Friday 13 January 2006 19:36, Graham Percival wrote: > OSX 10.3.9, 2.7.27-4. > > w154-mac:~/Apps/LilyPond.app/Contents/Resources/bin gpermus$ > ./lilypond-book --version > Traceback (most recent call last): >File "./lilypond-book", line 62, in ? > import lilylib as ly > ImportError: No module named lilylib > The same error comes up in my installation of 2.7.27-4 on Mandriva 2006. It also did not create the script for lilypond-book in /usr/local/bin, so I had to create one from the script of Lilipond itself (cp + vi). It seems that it was not correctly put in the .tar.bzip2-file, or something was forgotten to be installed. BTW: There is no need for two slashes next to each other in a path-name / fully qualified filename. == Herman Grootaers ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: Error in installer?
On Thursday 12 January 2006 20:31, Paul Scott wrote: > Saulo Falcão wrote: > >Hello, > > > >I think there is an error in this installer: > >http://lilypond.org/download/binaries/linux-x86/lilypond-2.7.27-1.li > >nux.sh > > > >At line 85 the tar command should be with options -xjf and NOT -xzf. > >Apparently the file is in bzip2 format and not in gzip. > >The entire line should be this: > >tail -c+1411 $0 | tar -C $lilydir -xjf > > That has been noted on the LilyPond user list but even that doesn't > fix it for me. > > Does it fix it for you? I noticed the same thing, and tried the mentioned change, but to no avail. The output is sequentially: -xzf; -xjf; and -xf. The last option is just to make sure it was not an uncompressed tar-file. ==> Start: Screendump of install 2.7.27-3 <<== [EMAIL PROTECTED] lily]# ./lilypond-2.7.27-3.linux.sh LilyPond installer for version 2.7.27 release 3. Use --help for help You're about to install lilypond in /usr/local/lilypond/ A script in /usr/local/bin/ will be created as a shortcut. Press ^C to abort, or Enter to proceed Making /usr/local/lilypond/ Creating script /usr/local/bin/lilypond Untarring ./lilypond-2.7.27-3.linux.sh bzip2: (stdin) is not a bzip2 file. tar: Child died with signal 13 tar: Afsluitcode uitgesteld na eerdere fouten To uninstall lilypond, do rm -r "/usr/local/bin/lilypond" "/usr/local/lilypond" [EMAIL PROTECTED] lily]# vi lilypond-2.7.27-3.linux.sh [EMAIL PROTECTED] lily]# ./lilypond-2.7.27-3.linux.sh LilyPond installer for version 2.7.27 release 3. Use --help for help You're about to install lilypond in /usr/local/lilypond/ A script in /usr/local/bin/ will be created as a shortcut. Press ^C to abort, or Enter to proceed Creating script /usr/local/bin/lilypond Untarring ./lilypond-2.7.27-3.linux.sh gzip: stdin: not in gzip format tar: Child died with signal 13 tar: Afsluitcode uitgesteld na eerdere fouten To uninstall lilypond, do rm -r "/usr/local/bin/lilypond" "/usr/local/lilypond" [EMAIL PROTECTED] lily]# vi lilypond-2.7.27-3.linux.sh [EMAIL PROTECTED] lily]# ./lilypond-2.7.27-3.linux.sh LilyPond installer for version 2.7.27 release 3. Use --help for help You're about to install lilypond in /usr/local/lilypond/ A script in /usr/local/bin/ will be created as a shortcut. Press ^C to abort, or Enter to proceed Creating script /usr/local/bin/lilypond Untarring ./lilypond-2.7.27-3.linux.sh tar: Dit ziet er niet uit als een tar-archief tar: Overslaan tot volgende kop tar: Archief bevat achterhaald-wordende grondtal-64 koppen tar: Gelezen 1448 bytes van - tar: Afsluitcode uitgesteld na eerdere fouten To uninstall lilypond, do rm -r "/usr/local/bin/lilypond" "/usr/local/lilypond" [EMAIL PROTECTED] lily]# ==> END: Screen-dump of install lilypond 2.7.27-3 <== Strange, because I am hoping this would resolve the installation of Lilypond om my mandriva system, which aborts when I try to create the fonts from the tar-ball of Lilypond 2.7.27. I also tried the shortcut mentioned in the install-procedure to retrieve the fonts with >> make -C mf get-pfa << but that gave the following message: >> Start screendump install fonts << [EMAIL PROTECTED] dev]# make -C mf get-pfa make: Entering directory `/home/herman/Documents/Lilypond/Lilypond/lilypond-2.7.27/mf' wget --passive-ftp -P ./out http://lilypond.org/download/binaries/Fedora-4/lilypond-2.7.27-1.i386.rpm --23:18:21-- http://lilypond.org/download/binaries/Fedora-4/lilypond-2.7.27-1.i386.rpm => `./out/lilypond-2.7.27-1.i386.rpm' Bezig met oplossen van lilypond.org... 82.94.241.173 Connecting to lilypond.org|82.94.241.173|:80... verbonden. HTTP verzoek verzonden, wacht op antwoord... 404 Not Found 23:18:22 FOUT 404: Not Found. make: *** [out/lilypond-2.7.27-1.i386.rpm] Fout 1 make: Leaving directory `/home/herman/Documents/Lilypond/Lilypond/lilypond-2.7.27/mf' [EMAIL PROTECTED] dev]# >> End screendump install fonts << Maybe someone has other ideas to get me up and running?? Yours, Herman Grootaers ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: [Laura Conrad] Lilypond-book problem
On Thursday 16 June 2005 10:10, Graham Percival wrote:
> On 15-Jun-05, at 6:54 AM, Mats Bengtsson wrote:
> > If you still see the problems, please send an example.
>
> I investigated, and discovered it was more particular than I
> though -- the problem occurs if you set \layout{ indent = BIG }
> (where BIG is bigger than it needs to be) in a non-\book format.
>
> So the problem _can_ still occur, but IMO this isn't worth
> fixing -- at least, there's still much worse problems (such as
> lilypond-book still not paying attention to the vertical spacing
> of a \book{} score)
>
> If you want to play, here's the file. Uncommenting either of
> the comments will fix the problem.
>
The trouble is that Latex, in my point of view, has a definition of the
papersize that is not-compatible with the output of lilypond-book. It tries
to use its own standards for margins on each paperformat it knows, not
knowing that lilypond, and thus lilypond-book, has its margins set by the
user.
What Latex tries to do is typesetting the systems it gets from lilypond-book
and the text in the lilypond-book-file, sees that there is space available on
a line and tries to place another system on the same line, failing to do so
because the second system is to large.
Therefore the hack of Mats is a good one. The final solution should be either
skipping Latex as a page-formatter, thus creating directly a ps-file from the
output of lilypond-book, or a valid lilypond-environment for Latex, which is
prefferably the better solution, because it may enable you to print the
output doublesided, without having to fuss with all kind of settings.
In the mean-time I edit the *systems.tex-files so that they insert a
newline-command after each system. I think that lilypond-book should generate
the file pre-, post-, and betweenLilyPond* in such a way that pre* and post*
contain "\relax" and between* "\newline", as a work-around, so we can have at
least one-sided pages of lilypond-book output, which is great for conductors
who need the total score, but for the performers who need only one part a
two-sided score is easier to handle.
Greetings
--
Herman Grootaers
___
lilypond-devel mailing list
lilypond-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: [Laura Conrad] Lilypond-book problem
On Saturday 11 June 2005 09:39, you wrote: > On 10-Jun-05, at 11:54 PM, Herman Grootaers wrote: > > I get a ps-file when I do: > > > > > > # :$ lilypond-book --format=latex --output=output --psfonts=psfonts > > liturgie.tex &>liturgie.log > > # :$ cd output > > # :$ latex liturgie.tex >>../liturgie.log 2>&1 > > # :$ dvips -o -h liturgie.psfonts liturgie >>../liturgie.log 2>&1 > > > > That's why the next command is ps2pdf. It's in the docs, 12.6. Is this > info lacking somewhere else? > Just that dvips with the option -o generates a ps-file, the option in the book 12.1 and following chapters make things more complex in my poinyt of view. I use a ps-file for bughunting the output, before converting it to pdf; xdvi gives me the general lay-out of a page, but not the details about each system. I mean here that it marks in red the boxes the place where a system should go, which is quite difficult to lay-out a book. When I was checking my last comment, found that in the documentation section 10.1 the output of creating titles has extra space above and is too much shifted to the left, killing in effect the leftmargin of the page. (just nit-picking;=)). > > > BTW, dvips yells that the fonts needed are not included into the > > ps-fonts-file, allthough output is correct. > > We know; there doesn't seem to be a way to stop it. > Pity, it should be mentioned in the documentation of the example of the piece from Han-Wen, so the users will know what they can expect as normal behaviour. It generates a lot less noice to the maintainers, when users know what they can expect, and the documentation becomes more clean, when bugs are removed. Not all output is bad (infamous trademark off-course), and they can see what is generally is normal, and what definitively is not usual. Thanks, Herman Grootaers ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: [Laura Conrad] Lilypond-book problem
On Saturday 11 June 2005 01:45, Laura Conrad wrote: > I reported this problem on June 3. It still exists on 2.5.30. > > > I got my lilypond-book problem down to a reasonable test file not > using wierd packages. There are two systems, and they're being placed > side by side rather than one above the other. Laura, I think this is a bug in 2.5.29 and later. I guess it is because Lilypond breaks a system when it thinks the linesize in the default staff-size is reached. It also seems to break a system when an alternative ending is started or reached, or when an explixit bar (\bar "|" ...) is reached. I have streamed all my sources, just to check this. I am running lilypond 2.5.29 on mandriva 2005LE on staff-size equal to 14 - this to reduce the amount of paper it generates - and my lilypond-book-file having no parameters for lilypond, all it has is the graphicx-package to get it running correctly. Note to the developers and documenters: Will you please update the section on lilypond-book because I think it is not completely up to date and/or correct. I get a ps-file when I do: # :$ lilypond-book --format=latex --output=output --psfonts=psfonts liturgie.tex &>liturgie.log # :$ cd output # :$ latex liturgie.tex >>../liturgie.log 2>&1 # :$ dvips -o -h liturgie.psfonts liturgie >>../liturgie.log 2>&1 BTW, dvips yells that the fonts needed are not included into the ps-fonts-file, allthough output is correct. Greetings, Herman Grootaers ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
Modificaion of the Paper-block
Gentlemen,
While I was studying the manual I got to te setting of the papersize.
Can the paper size not better set in the following way:
%%%
\paper { \size = \a4
\topMargin = 1 \cm
\leftMargin = 1.5 \cm
\rihgtMargin = 1 \cm
\bottomMargin = 1 \cm
}
%%%
This in my opinion more consistent with the way Lilypond works.
Can you also include in the documentation what Lilypond uses for a default
when not using an explicitly given value for each of those parameters.
Thanks in advance,
Herman Grootaers
___
lilypond-devel mailing list
lilypond-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: option --ps doesn't behave correctly
On Saturday 07 May 2005 23:59, Paul Scott wrote: > Werner LEMBERG wrote: > >If I say > > > > lilypond --ps foo.ly > > > >I expect to get `foo.ps', and nothing else, but lilypond always runs > >ps2pdf to produce a PDF file. > > What version? It works fine on 2.4.x. > > Paul Scott > I geuss he is using the 2.5.2x tree, because I have the same problems with this command-line. Lilypond -f ps foo.ly works though, so I am using that to do the works. -- Herman Grootaers ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: Strange programming error
On Wednesday 27 April 2005 15:53, David Bobroff wrote:
> In recent CVS I'm getting this:
>
> GNU LilyPond 2.5.21
> Processing `/home/david/dean/ode/test.ly'
> Parsing...
> Interpreting music... [3]
> Preprocessing graphical objects...
> Calculating line breaks...
> programming error: Stem has no extent in Slur_score_state
> continuing, cross fingers
> programming error: Stem has no extent in Slur_score_state
> continuing, cross fingers
> Calculating page breaks...
> Layout output to `test.ps'...
> Converting to `test.pdf'...
>
> When processing this:
>
> \version "2.5.21"
>
> mus = \relative c' {
> \key d \major
> \clef F
> a2-( cis
> a1-)
> }
>
> \score {
> \relative c' {
> \mus
> }
> }
>
> The output look ok, but it is weird to get this error from apparently
> legitimate input.
>
I get the same results when I was compiling a piece for our churchchoir.
The output is defective, because a slur is not completed over a break, just as
a descrecendo in the following snippet from that piece:
\header
{ maintainer = "Lezer Herman (Grootaers)"
lastupdated = "2003/07/08"
}
\version "2.5.19"
global =
{ \key f \major
\time 4/4
\autoBeamOff
}
sop = \relative c''
{
bes2.^\>( a4^\( \break
a4.^\!^\))^\p g8 g4 r
}
alt = \relative c'
{
g2._\>( f4_\( f4._\!_\))_\p e8 e4 r
}
ten = \relative c'
{
c1^\>( c4.^\!)^\p c8 c4 r
}
bas = \relative c
{
e2._\>( f4_\( c4._\!_\))_\p c8 c4 r
}
koor = \lyricmode
{
ÐÐ- ÑÐ- ÐÐ- ÑÑ
}
\score
{ \context ChoirStaff
<< \context Staff = "women"
<< \context Voice = "soprano"
{ \voiceOne << \global \sop >> }
\context Voice = "alto"
{ \voiceTwo << \global \alt >> }
\context Lyrics = alto { s1 }
>>
\context Staff = "men"
<< \clef bass
\context Voice = "tenor"
{ \voiceOne << \global \ten >> }
\context Voice = "bass"
{ \voiceTwo << \global \bas >> }
>>
\context Lyrics = alto \lyricsto alto \koor
>>
\layout { indent = 0.0\mm
raggedright=##t
raggedlast=##t
\context
{ \Staff }
}
}
%%%%%%
I am trying to file a bug-report about this, but I do not know if this is
succeeded.
BTW.: Does anybody know how I can get an indication on which part is sung
where, usually it is Soprane, Alto, Tenor, and Bass, but in the scores I get
they are sometimes changed, because they are taken from copies of old books.
--
Herman Grootaers
[EMAIL PROTECTED]
___
lilypond-devel mailing list
lilypond-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: 'make all' fails
On Thursday 28 October 2004 10:52, you wrote: > The log says > > > ./out/macros.texi:98: Onbekend commando `ifdocbook'. > > which means build depends should require makeinfo 4.7. > Thanks, Jan, for the info, but then configure should have given an error. I will get the makeinfo rpm to get it working again. Thanks again. -- Herman Grootaers ___ lilypond-devel mailing list [EMAIL PROTECTED] http://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: 'make all' fails
On Thursday 28 October 2004 08:40, David Bobroff wrote: > As of CVS ChangeLog 1.2763 I get a 'make all' failure: > > Compiling ./out/music-glossary.texi... > Processing include: macros.itexi > Reading macros.itexi... > Dissecting... > Writing snippets... > All snippets are up to date... > Compiling ./out/macros.texi... > mv ./out/music-glossary.texinfo out/music-glossary.nexi 2>/dev/null || > mv ./out/music-glossary.texi out/music-glossary.nexi > if [ 4007000 -le 4006000 ]; then \ > (cd ./out && \ > ls -1 lily-*.ly | sed 's/.ly$/.txt/' | xargs touch) || true; \ > fi > LANG= makeinfo --enable-encoding -I ./out > --output=./out/music-glossary.info out/music-glossary.nexi > out/music-glossary.nexi:5707: Unknown command `loggingall'. > makeinfo: Removing output file `./out/music-glossary.info' due to > errors; use --force to preserve. > make[2]: *** [out/music-glossary.info] Error 1 > rm out/music-glossary.nexi > make[2]: Leaving directory `/usr/src/lilypond/Documentation/user' > make[1]: *** [all] Error 2 > make[1]: Leaving directory `/usr/src/lilypond/Documentation' > make: *** [all] Error 2 > On my mandrake 10.0 box, fully patched, I got a seg-fault on the documentation when I tried to make all on the tar-ball of 2.3.24. Make install dumped its core on the same place it looks like, but I forgot to append the output to the logfile. The coredump was not alas saved. What I did notice was that 2.3.23 seems to have the same problem on the same place, but it did not give no error messages, and it did do a successfull make install. The original log file: [EMAIL PROTECTED] dev]$ lla make.log -rw-r--r-- 1 herman herman 4549063 okt 27 09:28 make.log [EMAIL PROTECTED] dev]$ wc make.log 97084 738441 4549063 make.log ** make.log # total of 9621 lines snipped make[1]: Entering directory `/home/herman/Documents/Lilypond/Lilypond/lilypond-2.3.24/Documentation' /home/herman/lily/dev/stepmake/stepmake/generic-targets.make:143: out/dummy.dep: No such file or directory please ignore innocent warning about dummy.dep mkdir -p ./out touch ./out/dummy.dep make[1]: Leaving directory `/home/herman/Documents/Lilypond/Lilypond/lilypond-2.3.24/Documentation' make[1]: Entering directory `/home/herman/Documents/Lilypond/Lilypond/lilypond-2.3.24/Documentation' make PACKAGE=LILYPOND package=lilypond -C user all && make PACKAGE=LILYPOND package=lilypond -C bibliography all && make PACKAGE=LILYPOND package=lilypond -C pictures all && make PACKAGE=LILYPOND package=lilypond -C topdocs all && make PACKAGE=LILYPOND package=lilypond -C misc all && true make[2]: Entering directory `/home/herman/Documents/Lilypond/Lilypond/lilypond-2.3.24/Documentation/user' /home/herman/lily/dev/stepmake/stepmake/generic-targets.make:143: out/dummy.dep: No such file or directory please ignore innocent warning about dummy.dep mkdir -p ./out touch ./out/dummy.dep make[2]: Leaving directory `/home/herman/Documents/Lilypond/Lilypond/lilypond-2.3.24/Documentation/user' make[2]: Entering directory `/home/herman/Documents/Lilypond/Lilypond/lilypond-2.3.24/Documentation/user' cd ./out && /home/herman/lily/dev/lily/out/lilypond --verbose /home/herman/Documents/Lilypond/Lilypond/lilypond-2.3.24/ly/generate-documentation LILYPOND_DATADIR="/usr/local/share/lilypond" LOCAL_LILYPOND_DATADIR=/usr/local/share/lilypond/2.3.24" LOCALEDIR="/usr/local/share/locale" LILYPONDPREFIX="/home/herman/lily/dev/share/lilypond" Nu wordt verwerkt `/home/herman/Documents/Lilypond/Lilypond/lilypond-2.3.24/ly/generate-documentation.ly' Ontleden... [/home/herman/lily/dev/share/lilypond/ly/init.ly[/home/herman/lily/dev/share/lilypond/ly/declarations-init.ly[/home/herman/lily/dev/share/lilypond/ly/music-functions-init.ly] [/home/herman/lily/dev/share/lilypond/ly/nederlands.ly] [/home/herman/lily/dev/share/lilypond/ly/drumpitch-init.ly] [/home/herman/lily/dev/share/lilypond/ly/chord-modifiers-init.ly] [/home/herman/lily/dev/share/lilypond/ly/script-init.ly] [/home/herman/lily/dev/share/lilypond/ly/scale-definitions-init.ly] [/home/herman/lily/dev/share/lilypond/ly/grace-init.ly] [/home/herman/lily/dev/share/lilypond/ly/midi-init.ly[/home/herman/lily/dev/share/lilypond/ly/performer-init.ly]] [/home/herman/lily/dev/share/lilypond/ly/paper-defaults.ly] [/home/herman/lily/dev/share/lilypond/ly/engraver-init.ly] [/home/herman/lily/dev/share/lilypond/ly/dynamic-scripts-init.ly] [/home/herman/lily/dev/share/lilypond/ly/spanners-init.ly] [/home/herman/lily/dev/share/lilypond/ly/property-init.ly]] [/home/herman/Documents/Lilypond/Lilypond/lilypond-2.3.24/ly/generate-documentation.ly]] [/home/herman/lily/dev/share/lilypond/scm/define-music-types.scm] [/home/herman/lily/dev/share/lilypond/scm/output-lib.scm] [/home/herman/lily/dev/share/lilypond/scm/c++.scm] [/home/herman/lily/dev/share/lilypond/scm/chord-ignatzek-names.scm] [/home/herman/lily/dev/share/lilypond/scm/chord-entry.scm] [/home/herman/lily/dev/share/lilypond/scm/chord-generic-names.scm] [/home/herma
Compile-error in 2.3.12
When I tried to compile Lilypond 2.3.12 from source, I got an error in one of
the documentation-files.
I resolved it by removing the "@" and the "{}" from line 65 of
lilypond-book.itely. I am not sure if that is correct to do so, but after the
change it compiled clean, and also installed nicely.
It is a good prgram, however it would be perfect if there would be support for
not latin1-characters. Maybe can you give me some hints where I can look for
in the sources.
--
Herman Grootaers
___
lilypond-devel mailing list
[EMAIL PROTECTED]
http://lists.gnu.org/mailman/listinfo/lilypond-devel
