<d...@gnu.org>: Tuesday, October 09, 2012 8:36 AM > On 2012/10/09 05:04:50, lemzwerg wrote: >> http://codereview.appspot.com/6635050/diff/1/Documentation/de/notation/pitches.itely#newcode1529 >> Documentation/de/notation/pitches.itely:1529: \accidentalStyle >> StaffGroup."voice" >> This looks strange. I don't expect double quotes after a dot. Any > better >> representation possibility? > > Agreed. _All_ of the following will work: > \accidentalStyle "StaffGroup.voice" > \accidentalStyle StaffGroup.voice > \accidentalStyle "StaffGroup"."voice" > > whereas everything involving #"Staffgroup..." will _not_ work (only > LilyPond strings autoconvert to symbols). > > I think I'd go for > \accidentalStyle Staffgroup.piano-cautionary > myself as then the temptation to employ Scheme strings by accident is > smaller, but then it seems inconsistent to use > \accidentalStyle "piano-cautionary" > so I'd crank open another convert-ly rule to turn those into > \accidentalStyle piano-cautionary > as well. Which makes for worse backward-compatibility of scores. > > What do people prefer to see?
As the 2.17 releases appear to be majoring on syntax changes I'd prefer to go for the most intuitive easily-learned syntax rather than backward compatibility. Let's get all the syntax changes incorporated in 2.17, then we can agree an immutable set ready for release 3. Trevor _______________________________________________ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
