> Hope they're in; see scm/chord-names.ly and input/test/american-chords.ly.
> If not, I'll hear from you, no?
You bet. ;-)
> Yes, I'll try to stay current, although I won't build binaries for
> LilyPond versions that introduce nasty flaws.
That's about what I figured--no use building a binary that's worse than the
previous one!
> I hope some of it works (apart from windows-specifig guile problems);
> we had quite some updates lately (eg kpathsea).
Well, it appears that 'kpathsea' support isn't working correctly in the
WinXX version (ly2dvi as well as lilypond runs follow):
C:\Temp\lilypond\Music>ly2dvi -P american-chords
ly2dvi (GNU lilypond) 1.3.74.jcn1
executing: ash -c "lilypond american-chords 2>&1"
GNU LilyPond 1.3.74.jcn1
Now processing: `american-chords.ly'
Parsing...warning: invalid subtraction: not part of chord: e
warning: invalid subtraction: not part of chord: e
Interpreting music...[6]
Preprocessing elements...
Calculating column positions... warning: can't find font: `cmr10'
warning: Loading default font
error: can't find default font: `cmr10'
ly2dvi hmm, I could not find an output file name
C:\Temp\lilypond\Music>lilypond american-chords.ly
GNU LilyPond 1.3.74.jcn1
Now processing: `american-chords.ly'
Parsing...warning: invalid subtraction: not part of chord: e
warning: invalid subtraction: not part of chord: e
Interpreting music...[6]
Preprocessing elements...
Calculating column positions... warning: can't find font: `cmr10'
warning: Loading default font
error: can't find default font: `cmr10'
I checked my miktex.ini file just to make sure miktex was looking in the
right place for the standard .tfm files, and this was in there:
;; Where MiKTeX searches for .tfm files.
TFMPath=.;%R\fonts\tfm//
According to the miktex documentation, it searches that directory and any
below it (where cmr10.tfm actually lives), so it should be finding it. I
would imagine that a symlink (like the older versions) wouldn't work. Any
ideas?
-- Shamus
