ChangeLog/1.4419 fails to compile correctly

2006-01-01 Thread Tapio Tuovila
Hi,

when trying to compile
ChangeLog/1.4419/Mon Jan  2 05:28:33 2006
on SuSE 10.0 it spits out the following:

 out/feta-braces-h.otf-table
cat out/feta-braces-i.lisp \
 \
 > out/feta-braces-i.otf-table
make[1]: *** No rule to make target
`/usr/share/fonts/default/Type1/c059013l.pfb', needed by
`out/CenturySchL-Ital.ttf'.  Stop.
make[1]: Leaving directory `/home/tapu/Downloads/Lily/lilypond/mf'
make: *** [all] Error 2



it is possible to try lily/out/lilypond, this gives the following:

lily/out/lilypond
GNU LilyPond 2.7.27
[/home/tapu/Downloads/Lily/lilypond/out/share/lilypond/2.7.27/scm/lily-library.scm]
[/home/tapu/Downloads/Lily/lilypond/out/share/lilypond/2.7.27/scm/file-cache.scm]
[/home/tapu/Downloads/Lily/lilypond/out/share/lilypond/2.7.27/scm/define-music-types.scm]
[/home/tapu/Downloads/Lily/lilypond/out/share/lilypond/2.7.27/scm/output-lib.scm]
[/home/tapu/Downloads/Lily/lilypond/out/share/lilypond/2.7.27/scm/c++.scm]
[/home/tapu/Downloads/Lily/lilypond/out/share/lilypond/2.7.27/scm/chord-ignatzek-names.scm]
[/home/tapu/Downloads/Lily/lilypond/out/share/lilypond/2.7.27/scm/chord-entry.scm]
[/home/tapu/Downloads/Lily/lilypond/out/share/lilypond/2.7.27/scm/chord-generic-names.scm]
[/home/tapu/Downloads/Lily/lilypond/out/share/lilypond/2.7.27/scm/stencil.scm]
[/home/tapu/Downloads/Lily/lilypond/out/share/lilypond/2.7.27/scm/markup.scm]
[/home/tapu/Downloads/Lily/lilypond/out/share/lilypond/2.7.27/scm/music-functions.scm]
[/home/tapu/Downloads/Lily/lilypond/out/share/lilypond/2.7.27/scm/part-combiner.scm]
[/home/tapu/Downloads/Lily/lilypond/out/share/lilypond/2.7.27/scm/autochange.scm]
[/home/tapu/Downloads/Lily/lilypond/out/share/lilypond/2.7.27/scm/define-music-properties.scm]
[/home/tapu/Downloads/Lily/lilypond/out/share/lilypond/2.7.27/scm/auto-beam.scm]
[/home/tapu/Downloads/Lily/lilypond/out/share/lilypond/2.7.27/scm/chord-name.scm]
[/home/tapu/Downloads/Lily/lilypond/out/share/lilypond/2.7.27/scm/parser-ly-from-scheme.scm]
[/home/tapu/Downloads/Lily/lilypond/out/share/lilypond/2.7.27/scm/define-context-properties.scm]
[/home/tapu/Downloads/Lily/lilypond/out/share/lilypond/2.7.27/scm/translation-functions.scm]
[/home/tapu/Downloads/Lily/lilypond/out/share/lilypond/2.7.27/scm/script.scm]
[/home/tapu/Downloads/Lily/lilypond/out/share/lilypond/2.7.27/scm/midi.scm]
[/home/tapu/Downloads/Lily/lilypond/out/share/lilypond/2.7.27/scm/layout-beam.scm]
/home/tapu/Downloads/Lily/lilypond/out/share/lilypond/2.7.27/scm/parser-clef.scm]
[/home/tapu/Downloads/Lily/lilypond/out/share/lilypond/2.7.27/scm/layout-slur.scm]
[/home/tapu/Downloads/Lily/lilypond/out/share/lilypond/2.7.27/scm/font.scm]
[/home/tapu/Downloads/Lily/lilypond/out/share/lilypond/2.7.27/scm/encoding.scm]
[/home/tapu/Downloads/Lily/lilypond/out/share/lilypond/2.7.27/scm/fret-diagrams.scm]
[/home/tapu/Downloads/Lily/lilypond/out/share/lilypond/2.7.27/scm/define-markup-commands.scm]
[/home/tapu/Downloads/Lily/lilypond/out/share/lilypond/2.7.27/scm/define-grob-properties.scm]
[/home/tapu/Downloads/Lily/lilypond/out/share/lilypond/2.7.27/scm/define-grobs.scm]
[/home/tapu/Downloads/Lily/lilypond/out/share/lilypond/2.7.27/scm/define-grob-interfaces.scm]
[/home/tapu/Downloads/Lily/lilypond/out/share/lilypond/2.7.27/scm/define-stencil-commands.scm]
[/home/tapu/Downloads/Lily/lilypond/out/share/lilypond/2.7.27/scm/layout-page-layout.scm]
[/home/tapu/Downloads/Lily/lilypond/out/share/lilypond/2.7.27/scm/titling.scm]
[/home/tapu/Downloads/Lily/lilypond/out/share/lilypond/2.7.27/scm/paper.scm]
[/home/tapu/Downloads/Lily/lilypond/out/share/lilypond/2.7.27/scm/backend-library.scm]
[/home/tapu/Downloads/Lily/lilypond/out/share/lilypond/2.7.27/scm/x11-color.scm]
[/home/tapu/Downloads/Lily/lilypond/out/share/lilypond/2.7.27/scm/safe-lily.scm]
Usage: lilypond [OPTION]... FILE...

Typeset music and/or produce MIDI from FILE.

LilyPond produces beautiful music notation.
For more information, see http://lilypond.org

Options:
  -b, --backend=BACK   use backend BACK (gnome, ps,eps,
 scm, svg, tex, texstr)
 default: PS
  -d, --define-default=SYM=VAL set a Scheme program option. Uses #t
if VAL is not specified
 Try -dhelp for help.
  -e, --evaluate=EXPR  evaluate scheme code
  -f, --formats=FORMATsdump FORMAT,...  Also as separate
options:
  --dvigenerate DVI (tex backend only)
  --relocate   relocate using directory of lilypond
program
  --pdfgenerate PDF (default)
  --pnggenerate PNG
  --ps generate PostScript
  --texgenerate TeX (tex backend only)
  -h, --help   print this help
  -H, --header=FIELD   dump a header field to file
BASENAME.FIELD
  -I, --include=DIRadd DIR to search path
  -i, --init=FILE  

Re: \renameouput? \renameinput?

2006-01-01 Thread Han-Wen Nienhuys

Graham Percival wrote:


On 1-Jan-06, at 3:47 PM, Bernard Hurley wrote:


The expression "\renameinput" seems a bit misleading, although I can see
where the name comes from, maybe it should be "\sourcefilename".



Or possibly "\displayinput", since it simply displays the name in 
quotations.  It currently isn't explained in the manual, so we don't 
really have to worry about confusing people with the name... but I 
_should_ add it at some point.


I think \sourcefilename is thet better one. I've changed it to that.


--
 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


Re: \renameouput? \renameinput?

2006-01-01 Thread Graham Percival


On 1-Jan-06, at 3:47 PM, Bernard Hurley wrote:

The expression "\renameinput" seems a bit misleading, although I can 
see

where the name comes from, maybe it should be "\sourcefilename".


Or possibly "\displayinput", since it simply displays the name in 
quotations.  It currently isn't explained in the manual, so we don't 
really have to worry about confusing people with the name... but I 
_should_ add it at some point.


Cheers,
- Graham



___
lilypond-devel mailing list
lilypond-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-devel


Re: \renameouput? \renameinput?

2006-01-01 Thread Bernard Hurley
The expression "\renameinput" seems a bit misleading, although I can see
where the name comes from, maybe it should be "\sourcefilename".

/Bernard

On Thu, 2005-12-29 at 11:26 +0100, Han-Wen Nienhuys wrote:
> Graham Percival wrote:
> > What does \renameinput do?  I was hoping to use it to rename the output, 
> > but it doesn't work.  I have a file (foo.ly), which I want to output to 
> > bar.pdf .
> > 
> > This is part of lilypond interactive mode, so I can't easily just rename 
> > the output with the shell.  Details about this will come very soon after 
> > I fix this issue.
> > 
> 
> This is meant for displaying something readable for lily-47382973.ly 
> when there is an error.
-- 
Bernard Hurley <[EMAIL PROTECTED]>


___
lilypond-devel mailing list
lilypond-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-devel


Re: Extending \lilypondfile to support separate handling of header fields for use by LaTeX et.al.

2006-01-01 Thread Michael Haynie
I found and fixed two problems with the LaTeX macros I sent out 
earlier, and revised the hymn song example format to move the copyright 
text to the end of the song.  The fix for header processing is a little 
ugly -- I think there must be a simpler way, but (a) it works, and (b) 
it doesn't materially increase processing time, which is still 
dominated by lilypond proper.


I'm still pretty happy with the mechanism this represents, but for two 
things.


* -Hall to extract every header would be would be tremendously useful. 
Otherwise, I have to extract all of the headers individually, and 
that's *really* tedious.


* markup in header text is not handled well at all.  I'm really not 
certain how to proceed -- the lilypond markup doesn't look much like 
the equivalent LaTeX markup, though some type of parser should be able 
to translate from one form to the other.  It would be easy to write 
such a filter in C/C++, but that would introduce yet another language 
into the mix.  Not a happy thought.  A top-down parser could be 
hand-written, I suppose.


As before, comments are welcome.



lilypondSystemMacros.tex
Description: TeX document




On Dec 29, 2005, at 8:08 AM, Bernard Hurley wrote:


Hi Michael,

On Tue, 2005-12-27 at 16:45 -0500, Michael Haynie wrote:
I had a good look at the proposed alternative mechanism as described 
in

lilypondmacros.  It mostly worked, but left me with a fair amount of
hand editing that would have to be revisited each time I rearranged 
the
songs in the book -- a *frequent* occurrence when I'm laying out a 
book

for final printing.  I studied what you did, and I've developed an
alternative suggestion, in several parts:


I've been fixing some of the bugs in my code (there were some really
silly ones like getting the system count wrong) and changing the way it
works. I will send you a new version soon.  I will also have a look at
you ideas which look interesting and see how I can take them into
account. But that will have to be after 3rd Jan as I have a lot of work
to do by then. Just one thing, since I will be realeasing by stuff 
under

GPL 2 or later, could you confirm that your files can be released uner
this license?

Regards,

Bernard


___
lilypond-devel mailing list
lilypond-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-devel


Re: lilypond processing mode example

2006-01-01 Thread Paul Scott

Graham Percival wrote:



On 31-Dec-05, at 5:09 AM, Bernard Hurley wrote:


Looks interesting but I don't seem to be able to download "makelily.pl".



Whoops!  The web server executed the script instead of sending it to 
you... anybody know how to make perl scripts downloadable?


You could zip it.

Paul Scott



___
lilypond-devel mailing list
lilypond-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-devel


Re: lilypond processing mode example

2006-01-01 Thread Bernard Hurley
Sorry, should have said:

RemiveHandler   .pl

I've been doing things with postscript files recently and have got the
extention etched into my brain!

On Sun, 2006-01-01 at 12:59 +, Bernard Hurley wrote:
> try putting the directive:
> 
>   RemoveHandler .ps
> 
> in a file called ".htaccess" in the same directory as the Perl script.
> 
> On Sat, 2005-12-31 at 15:35 -0800, Graham Percival wrote:
> > On 31-Dec-05, at 5:09 AM, Bernard Hurley wrote:
> > 
> > > Looks interesting but I don't seem to be able to download 
> > > "makelily.pl".
> > 
> > Whoops!  The web server executed the script instead of sending it to 
> > you... anybody know how to make perl scripts downloadable?  For now 
> > I'll just send it privately to anybody who's interested.
> > 
> > Cheers,
> > - Graham
> > 
-- 
Bernard Hurley <[EMAIL PROTECTED]>


___
lilypond-devel mailing list
lilypond-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-devel


Re: osx 2.7.26 backend failure

2006-01-01 Thread Han-Wen Nienhuys

Graham Percival wrote:

Hi all,

10.3.9, most recent fink, no packages installed manually, 2.7.26  
release from cvs, no extra patches (other than the one in  
./darwin.patch, which does the istream/iostream/std thing).


Test file is foo.ly:
{ c'4 }


lilypond foo.ly works perfectly.
lilypond -b=ps foo.ly  fails.  Yes, I know that -b=ps  should work  
exactly like having no arguments.  Any ideas?  I've got gdb installed,  



try -b ps

we don't have a "=ps" backend.


--
 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


Re: lilypond processing mode example

2006-01-01 Thread Bernard Hurley
try putting the directive:

RemoveHandler .ps

in a file called ".htaccess" in the same directory as the Perl script.

On Sat, 2005-12-31 at 15:35 -0800, Graham Percival wrote:
> On 31-Dec-05, at 5:09 AM, Bernard Hurley wrote:
> 
> > Looks interesting but I don't seem to be able to download 
> > "makelily.pl".
> 
> Whoops!  The web server executed the script instead of sending it to 
> you... anybody know how to make perl scripts downloadable?  For now 
> I'll just send it privately to anybody who's interested.
> 
> Cheers,
> - Graham
> 
-- 
Bernard Hurley <[EMAIL PROTECTED]>


___
lilypond-devel mailing list
lilypond-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-devel