I use transposition a lot with figured bass. I avoid the problem by adopting the "early" convention where no natural sign exists, only sharp and flat. In this way, no changes are needed to the figures after transposition. It takes some extra mental effort (you see a flat above the bass note D and have to play F-natural ...) but this was the normal notation before about 1750. If you would really like to transform bass figures for transposition you could use a pre-processor - Denemo for instance has a scriptable interface that would allow you to transpose the figures before generating the LilyPond text.
Richard Shann. On Wed, 2013-02-13 at 00:31 +0100, Xavier Scheuer wrote: > On 12 February 2013 12:40, Joseph Rushton Wakeling > <joseph.wakel...@webdrake.net> wrote: > > On 02/12/2013 03:05 AM, David Kastrup wrote: > >> > >> The advantage LilyPond has over the hand engraver is that it does not > >> need to say "I don't make mistakes". The hand engraver puts down the > >> staff lines, and short of throwing the plate(s) away and starting over, > >> the layout has to fit those lines, and the page breaks have to match > >> those bars in eternity. And "give me that transposed for Bb" is an > >> inexpensive option, as well as "can you play that for me?". > > > > > > That's something of a dangerous assumption. Consider this little snippet, > > where a trill-with-accidental is included according to the instructions on > > articulations and ornamentations: > > http://lilypond.org/doc/v2.16/Documentation/notation/expressive-marks-attached-to-notes#articulations-and-ornamentations > > Speaking of accidentals not correctly handled when using transposition: > the current implementation of figured bass in LilyPond is only > graphical (contrary to chords/chordmode). > > It is possible to add accidentals to the figures with + ! -, but since > figuremode is not (currently) somehow "linked" to notes, these > accidentals are not correctly modified when the piece is transposed. > > I do not see how one could do that, nor if this "feature" is really > asked/needed a lot, the amount of work or possible compatibility breaks, > hence before submitting a feature request to bug-lilypond, I would like > to know your thoughts about this. > > Cheers, > Xavier > _______________________________________________ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
