[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: transposition

From: Mats Bengtsson
Subject: Re: transposition
Date: Wed, 02 Aug 2006 10:25:56 +0200
User-agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.13) Gecko/20060417

Graham Percival wrote:

Ady Ecker wrote:

Thank you for your quick response. I was able to make it work.

Please keep lilypond email on the mailing list, so that other people can benefit from the discussion.

It would help if -
1. This would be the default behavior of \transpose (this will save many
questions in the future)

I don't think this will happen; in many cases the current behavior of \transpose is the desired one. From a music theory standpoint, it's the correct one.

Agree completely! As a violin player, I often get very confused if the editor
has made an enharmonic replacement of some note just to reduce the number
of accidentals, both since it makes it harder to understand the melody and
harder to find a natural fingering. I guess the sitiuation may be different
if you play woodwind instruments, for example.

3. In the file collated-files.pdf , make some note that smart-transpose.ly is actually a link. It took me some time to realize that the html version is
different and has a link behind it.

This would require some advanced modifications to the documentation compiling process; I don't know how to do it. I agree that it would be nice, but it would take me a few hours to figure it out. I would welcome any patch that does this, though.

Why not simply add a few lines to the introductory text at the top of the document
(i.e. in input/test/+.ly), saying something like:

"In the on-line web version of this document, you can click on the file name
or figure for each example to see the corresponding input file."

4. The name of the file behind smart-transpose.ly is not
"smart-transpose.ly". It is a bit confusing. I would suggest writing a
comment in this file saying what to do with it (i.e. cut from here to here, save in this name, and in your main file do include etc).

Could you do this? Make the modifications to smart-transpose and send the new file to the list; I'll add it to the docs.

Probably what he has in mind are the automatically generated file names
like "lily-1341618135.ly" that lilypond-book produces.
The files already now contain comments on what lines should be
cut/pasted, but I guess that formulation could be made less cryptic.

Information on how to put general definitions in a separate file that can
be included in the score files, mainly belong to the main manual. See for
example "4.1.1 General suggestions" and "4.3 Style sheets" in the manual.


reply via email to

[Prev in Thread] Current Thread [Next in Thread]