>> I haven’t implemented the double-C cases yet. > > This is what I think would be best: > > * leave the default style alone > * add to the C style: 4/2 -> CC, 2/1 -> cut-CC > > This would end the equivalence of default and C styles. Does that seem like > a bad idea to any seasoned Lilypond developers? I would prefer to hear it > now than to implement it first and hear about it in code review. > > My reasoning is that the CC and cut-CC time signatures seem too obscure to be > enabled by default, but too closely related to the C and cut-C time > signatures to deserve a separate style. The new time signatures would make > sense within this matrix: > > numbered single-digit > C single-C
Hi Dan, it is not my intention to bother you, but I would like to understand this. Is this your plan? style default c ¢ 2/4 2/1 4/2 8/4 3/4 6/8 C c ¢ 2/4 ¢¢ cc 8/4 3/4 6/8 <--- single-C c ¢ 2/4 ¢ c 8/4 3/4 6/8 <--- numbered 4/4 2/2 2/4 2/1 4/2 8/4 3/4 6/8 single-digit 4 2 2 2 4 8 3 6 With this meaning: - I indicate the C symbols with c and ¢ - a mono space font needed - default means the current C style - C means your C style Will single-digit be renamed to single-number? Source for showing time signatures: \version "2.18.2" %http://www.lilypond.org/doc/v2.18/Documentation/internals/time_002dsignature_002dinterface music = { \time 4/4 s1 \time 2/2 s \time 2/4 s2 \time 2/1 s1*2 \time 4/2 s \time 8/4 s \time 3/4 s2. \time 6/8 s2. } << \new Staff { \override Staff.TimeSignature.style = #'default <>^"default" \music } \new Staff { \override Staff.TimeSignature.style = #'C <>^"C" \music } %\new Staff { \override Staff.TimeSignature.style = #'single-C <>^"single-C" \music } \new Staff { \override Staff.TimeSignature.style = #'numbered <>^"numbered" \music } \new Staff { \override Staff.TimeSignature.style = #'single-digit <>^"single-digit" \music } \new Staff { \override Staff.TimeSignature.style = #'mensural <>^"mensural" \music } \new Staff { \override Staff.TimeSignature.style = #'neomensural <>^"neomensural" \music } >> Cheers, Joram _______________________________________________ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
