various problems using lilypond 1.3.111

[Michael Vanier]

Hi,

I'm in the process of converting a variety of files from older lilypond
versions (1.2.16) to 1.3.111.  I'm running this on a generic RH Linux 6.1
system using python 2.0 and guile 1.4.  Here are some of the problems I've
been having.

1) "convert-ly" doesn't work out-of-the-box because of changes in python
   2.0.  Specifically, the "append" list method will not wrap multiple
   arguments into a tuple; you have to specify it manually.  This means
   that all calls to append need extra parens around them e.g.

       conversions.append (
        (0,1,20), conv, 'deprecated \\textstyle, new \key syntax')

   should be

       conversions.append (
        ((0,1,20), conv, 'deprecated \\textstyle, new \key syntax'))

   After that the program works.  This should also be downward compatible
   with python 1.6.

2) I've been unable to figure out a way to specify a bass clef for any .ly
   files.  The old system doesn't work, and I can't get any of the test
   files to give me a bass clef either (e.g. inputs/test/clefs.ly).  Side
   note: the test files don't have a single standard for this either, with
   some using

       \clef "bass";

   and others

       \clef bass;

   What is the correct way to do this?  The documentation barely mentions
   this. 

   BTW many of the test files generate fatal errors when run through
   ly2dvi.  I can supply a list if you're interested.

3) I'm having several problems with the following test file:

   % test.ly

   \version "1.3.111"

   \include "english.ly"
   \include "paper16.ly"


   \header 
   {
        title = "title";
        composer = "composer";
        tagline = "";
   }


   melodya = 
    \notes \relative c % c'' 
    {
        \clef "bass";
        s2 e4. d8 |
        cs1 ~ |
        cs2 e4.  d8 |
        cs1 ~ | \break
        cs2 [ a8 b cs ds ] |
        [ e8 cs ds e ] [ cs8 ds e ds ] | 
        [ e8 cs ds e ] [ cs8 ds e cs ] | 
        ds1 ~ | \break
        ds2 fs4. e8  | 
        ds1 ~ | 
        ds2 [ b8 cs ds e ] | 
        [ fs8 ds e fs ] [ ds8 e fs e ] | \break
        [ fs8 ds e fs ] [ ds8 e fs ds8 ] |
        e1 ~ |
        e2 [ c8 d e fs ] | 
        [ g8 e fs g ] [ e8 fs g fs ] | \break 
        \bar "|." ;
   }


   \score 
   {
        \context PianoStaff 
        \notes 
        <
            \context Staff = melodya 
            <
                \clef "bass";
                \time 4/4;
                \key e \minor;
                \melodya
            >
        >

        \paper 
        {
            indent    = 0.0;
            linewidth = 15.0 \cm;
        }
   }

   % End of test.ly


   First off, my \break directives are not all being obeyed.  Specifically,
   the first two are while the last is not.  This forces eight bars onto
   one line, which looks bad.

   Second, I get the following mysterious warning:

       Failed typecheck for `glyph', value `brace' must be of type string

   with no line number.  What does this mean?

   Third, when I run the resulting dvi file through dvips, I get lots of
   warnings:
   
This is dvips(k) 5.86 Copyright 1999 Radical Eye Software (www.radicaleye.com)
' TeX output 2000.11.27:0033' -> test.ps
<texc.pro><special.pro>. [1
dvips: Unknown keyword (test.ly) in \special will be ignored
dvips: Couldn't find figure file src:52:30; continuing
dvips: Unknown keyword (test.ly) in \special will be ignored
dvips: Couldn't find figure file src:26:13; continuing
dvips: Unknown keyword (test.ly) in \special will be ignored
dvips: Couldn't find figure file src:26:13; continuing
dvips: Unknown keyword (test.ly) in \special will be ignored
dvips: Couldn't find figure file src:25:21; continuing
dvips: Unknown keyword (test.ly) in \special will be ignored
dvips: Couldn't find figure file src:25:21; continuing
dvips: Unknown keyword (test.ly) in \special will be ignored
dvips: Couldn't find figure file src:25:18; continuing
dvips: Unknown keyword (test.ly) in \special will be ignored
dvips: Couldn't find figure file src:25:18; continuing
dvips: Unknown keyword (test.ly) in \special will be ignored
dvips: Couldn't find figure file src:24:13; continuing
dvips: Unknown keyword (test.ly) in \special will be ignored
dvips: Couldn't find figure file src:25:13; continuing
dvips: Unknown keyword (test.ly) in \special will be ignored
dvips: Couldn't find figure file src:25:13; continuing
dvips: Unknown keyword (test.ly) in \special will be ignored
dvips: Couldn't find figure file src:24:13; continuing
dvips: Unknown keyword (test.ly) in \special will be ignored
dvips: Couldn't find figure file src:23:19; continuing
dvips: Unknown keyword (test.ly) in \special will be ignored
dvips: Couldn't find figure file src:23:19; continuing
dvips: Unknown keyword (test.ly) in \special will be ignored
dvips: Couldn't find figure file src:23:16; continuing
dvips: Unknown keyword (test.ly) in \special will be ignored
dvips: Couldn't find figure file src:23:16; continuing
dvips: Unknown keyword (test.ly) in \special will be ignored
dvips: Couldn't find figure file src:52:30; continuing
dvips: Unknown keyword (test.ly) in \special will be ignored
dvips: Couldn't find figure file src:30:13; continuing
dvips: Unknown keyword (test.ly) in \special will be ignored
dvips: Couldn't find figure file src:30:13; continuing
dvips: Unknown keyword (test.ly) in \special will be ignored
dvips: Couldn't find figure file src:29:38; continuing
dvips: Unknown keyword (test.ly) in \special will be ignored
dvips: Couldn't find figure file src:29:38; continuing
dvips: more errors in special, being ignored . . .
dvips: (perhaps dvips doesn't support your macro package?)
dvips: Couldn't find figure file src:29:36; continuing
dvips: Couldn't find figure file src:29:36; continuing
dvips: Couldn't find figure file src:29:33; continuing
dvips: Couldn't find figure file src:29:33; continuing
dvips: Couldn't find figure file src:29:31; continuing
dvips: Couldn't find figure file src:29:24; continuing
dvips: Couldn't find figure file src:29:31; continuing
dvips: Couldn't find figure file src:29:22; continuing
dvips: Couldn't find figure file src:29:22; continuing
dvips: Couldn't find figure file src:29:20; continuing
dvips: Couldn't find figure file src:29:20; continuing
dvips: Couldn't find figure file src:29:18; continuing
dvips: Couldn't find figure file src:29:18; continuing
dvips: Couldn't find figure file src:29:15; continuing
dvips: Couldn't find figure file src:29:9; continuing
dvips: Couldn't find figure file src:29:15; continuing
dvips: Couldn't find figure file src:28:38; continuing
dvips: Couldn't find figure file src:28:38; continuing
dvips: Couldn't find figure file src:28:36; continuing
dvips: Couldn't find figure file src:28:36; continuing
dvips: Couldn't find figure file src:28:33; continuing
dvips: Couldn't find figure file src:28:33; continuing
dvips: Couldn't find figure file src:28:31; continuing
dvips: Couldn't find figure file src:28:24; continuing
dvips: Couldn't find figure file src:28:31; continuing
dvips: Couldn't find figure file src:28:22; continuing
dvips: Couldn't find figure file src:28:22; continuing
dvips: Couldn't find figure file src:28:20; continuing
dvips: Couldn't find figure file src:28:20; continuing
dvips: Couldn't find figure file src:28:18; continuing
dvips: Couldn't find figure file src:28:18; continuing
dvips: Couldn't find figure file src:28:15; continuing
dvips: Couldn't find figure file src:28:9; continuing
dvips: Couldn't find figure file src:28:15; continuing
dvips: Couldn't find figure file src:27:26; continuing
dvips: Couldn't find figure file src:27:26; continuing
dvips: Couldn't find figure file src:27:24; continuing
dvips: Couldn't find figure file src:27:24; continuing
dvips: Couldn't find figure file src:27:21; continuing
dvips: Couldn't find figure file src:27:21; continuing
dvips: Couldn't find figure file src:27:18; continuing
dvips: Couldn't find figure file src:27:13; continuing
dvips: Couldn't find figure file src:27:18; continuing
dvips: Couldn't find figure file src:26:13; continuing
dvips: Couldn't find figure file src:27:13; continuing
dvips: Couldn't find figure file src:27:13; continuing
dvips: Couldn't find figure file src:38:36; continuing
dvips: Couldn't find figure file src:38:36; continuing
dvips: Couldn't find figure file src:38:34; continuing
dvips: Couldn't find figure file src:38:34; continuing
dvips: Couldn't find figure file src:38:31; continuing
dvips: Couldn't find figure file src:38:31; continuing
dvips: Couldn't find figure file src:38:29; continuing
dvips: Couldn't find figure file src:38:23; continuing
dvips: Couldn't find figure file src:38:29; continuing
dvips: Couldn't find figure file src:38:21; continuing
dvips: Couldn't find figure file src:38:21; continuing
dvips: Couldn't find figure file src:38:19; continuing
dvips: Couldn't find figure file src:38:19; continuing
dvips: Couldn't find figure file src:38:17; continuing
dvips: Couldn't find figure file src:38:17; continuing
dvips: Couldn't find figure file src:38:14; continuing
dvips: Couldn't find figure file src:38:9; continuing
dvips: Couldn't find figure file src:38:14; continuing
dvips: Couldn't find figure file src:37:24; continuing
dvips: Couldn't find figure file src:37:24; continuing
dvips: Couldn't find figure file src:37:22; continuing
dvips: Couldn't find figure file src:37:22; continuing
dvips: Couldn't find figure file src:37:19; continuing
dvips: Couldn't find figure file src:37:19; continuing
dvips: Couldn't find figure file src:37:17; continuing
dvips: Couldn't find figure file src:37:12; continuing
dvips: Couldn't find figure file src:37:17; continuing
dvips: Couldn't find figure file src:36:12; continuing
dvips: Couldn't find figure file src:37:12; continuing
dvips: Couldn't find figure file src:37:12; continuing
dvips: Couldn't find figure file src:36:12; continuing
dvips: Couldn't find figure file src:35:40; continuing
dvips: Couldn't find figure file src:35:40; continuing
dvips: Couldn't find figure file src:35:37; continuing
dvips: Couldn't find figure file src:35:37; continuing
dvips: Couldn't find figure file src:35:34; continuing
dvips: Couldn't find figure file src:35:34; continuing
dvips: Couldn't find figure file src:35:31; continuing
dvips: Couldn't find figure file src:35:25; continuing
dvips: Couldn't find figure file src:35:31; continuing
dvips: Couldn't find figure file src:35:23; continuing
dvips: Couldn't find figure file src:35:23; continuing
dvips: Couldn't find figure file src:35:21; continuing
dvips: Couldn't find figure file src:35:21; continuing
dvips: Couldn't find figure file src:35:18; continuing
dvips: Couldn't find figure file src:35:18; continuing
dvips: Couldn't find figure file src:35:16; continuing
dvips: Couldn't find figure file src:35:9; continuing
dvips: Couldn't find figure file src:35:16; continuing
dvips: Couldn't find figure file src:34:38; continuing
dvips: Couldn't find figure file src:34:38; continuing
dvips: Couldn't find figure file src:34:36; continuing
dvips: Couldn't find figure file src:34:36; continuing
dvips: Couldn't find figure file src:34:34; continuing
dvips: Couldn't find figure file src:34:34; continuing
dvips: Couldn't find figure file src:34:31; continuing
dvips: Couldn't find figure file src:34:25; continuing
dvips: Couldn't find figure file src:34:31; continuing
dvips: Couldn't find figure file src:34:23; continuing
dvips: Couldn't find figure file src:34:23; continuing
dvips: Couldn't find figure file src:34:21; continuing
dvips: Couldn't find figure file src:34:21; continuing
dvips: Couldn't find figure file src:34:18; continuing
dvips: Couldn't find figure file src:34:18; continuing
dvips: Couldn't find figure file src:34:16; continuing
dvips: Couldn't find figure file src:34:9; continuing
dvips: Couldn't find figure file src:34:16; continuing
dvips: Couldn't find figure file src:33:26; continuing
dvips: Couldn't find figure file src:33:26; continuing
dvips: Couldn't find figure file src:33:24; continuing
dvips: Couldn't find figure file src:33:24; continuing
dvips: Couldn't find figure file src:33:22; continuing
dvips: Couldn't find figure file src:33:22; continuing
dvips: Couldn't find figure file src:33:19; continuing
dvips: Couldn't find figure file src:33:13; continuing
dvips: Couldn't find figure file src:33:19; continuing
dvips: Couldn't find figure file src:32:13; continuing
dvips: Couldn't find figure file src:33:13; continuing
dvips: Couldn't find figure file src:33:13; continuing
dvips: Couldn't find figure file src:32:13; continuing
dvips: Couldn't find figure file src:31:22; continuing
dvips: Couldn't find figure file src:31:22; continuing
dvips: Couldn't find figure file src:31:18; continuing
dvips: Couldn't find figure file src:31:18; continuing
dvips: Couldn't find figure file src:30:13; continuing
dvips: Couldn't find figure file src:31:14; continuing
dvips: Couldn't find figure file src:31:14; continuing
] 
xdvi test.dvi


    I don't have a clue what's going on here.  Any ideas?

Thanks,

Mike

--------------------------------------------------------------
Mike Vanier     address@hidden
Department of Computation and Neural Systems, Caltech 216-76
GNU/Linux: We can't lose; we're on a mission from God.