Re: Assertion "source" failed: file "string.cc", line 67

[Mats Bengtsson]

> Hi,
> 
>    For some time now, I've been having problems with certain
>    files,  and  since this error occured to somebody else, I
>    figured  it  wasn't just me. Sometimes, I don't know why,
>    this error occurs in LY2DVI :
> 
> Preprocessing elements...
> Calculating column positions... kpathsea: Running mktextfm  feta-nummer10
> mktextfm: not found
> kpathsea: Appending font creation commands to missfont.log.
> assertion "source" failed: file "string.cc", line 67
>       0 [sig] lilypond 1880417 open_stackdumpfile: Dumping stack trace to 
> LILYPOND.EXE.stackdump
> 
>    The  last  time  this  happened  to  me  was  when  I was
>    compiling  a  Mazurka  by  Chopin downloaded from Mutopia
>    (wasn't  for  me). Now I'm really not sure this is a bug,
>    but I don't know what it is.

I've seen this happen for Lilypond files that use other
text fonts than the default cmr10. The reason is that
the font file searching routines in Lilypond doesn't
cooperate well with MiKTeX. However, feta-nummer10 is
a font which is included with the Lilypond distribution
and shouldn't any such problems. 
Please verify that the file /feta-nummer10.tfm exists in
some directory listed in $TFMFONTS (it should be in 
/usr/lilypond-1.4.5/share/lilypond/tfm).

If you get similar error messages for a font file 'cm*'
(for example cmti6 or cmbx12), then you could install
the font manually in the Lilypond directory tree:
(let's say you need cmbx12)

- Search for the file cmbx12.tfm in the MiKTeX directory 
  trees. If it doesn't exist, run the command 'latex testfont'
  in an ordinary DOS shell and input cmbx12 when prompted for 
  a font to test, followed by \table and \bye. 
  Then, repeat the file search.

- Copy the file to the directory 
  c:\cygwin\usr\lilypond-1.4.5\share\lilypond\tfm\

- Now ly2dvi should work correctly!

It should also be possible to add the path to the MiKTeX
directory where you found the cm*.tfm file to the 
environment variable $TFMFONTS (should be possible to 
automize in the installation scripts).
Unless we find any command line MiKTeX equivalent of
mktextfm, we still have to wait for a cygwin version of
teTeX to solve this problem completely, though.

   /Mats