Re: various problems using lilypond 1.3.111

[Mats Bengtsson]

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

Could you please send a patch to Han-Wen and Jan
(diff -u convert-ly.py.orig convert-ly.py).

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

Please read the FAQ on messed up symbols at
http://appel.lilypond.org/wiki/index.php?PostProcessing

> 3) I'm having several problems with the following test file:
   ...
> 
>    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.

I have no clue on this one.

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

This is a bug in 1.3.111, see the patch posted to gnu-music-discuss,
http://mail.gnu.org/pipermail/gnu-music-discuss/2000-November/000704.html

>    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
  ...
> 
>     I don't have a clue what's going on here.  Any ideas?

This is also in tbe FAQ, see
http://appel.lilypond.org/wiki/index.php?PostProcessing

   /Mats