Re: Horizontal alignment of DynamicTextSpanner left text
Le 31/01/2022 à 16:54, Simon Albrecht a écrit : Hello list, normally, horizontal alignment of grobs to other grobs is adjusted using self-alignment-X and parent-alignment-X—IIRC, this was homogenised some a couple years ago. However, when wanting to adjust the alignment of a DynamicTextSpanner’s left bound, I found that this is much less clear for spanners. They have the parent-alignment-X component hidden behind the misleading property name attach-dir, and no default way of adjusting self-alignment-X via grob property (see this thread [1] for workarounds). I suggest modifying line-spanner-interface to use self-alignment-X and parent-alignment-X in all subproperties of bound-details, and heeding these properties for DynamicTextSpanner and similar grobs. Best, Simon [1] https://lists.gnu.org/archive/html/lilypond-user/2022-01/msg00389.html Do you have some knowledge of C++? Unlike vertical placement, which is a little subtler, horizontal placement in lily/line-spanner.cc is quite straightforward. I'd expect a patch for this not to require extensive knowledge of internals. Best, Jean ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Horizontal alignment of DynamicTextSpanner left text
Hello list, normally, horizontal alignment of grobs to other grobs is adjusted using self-alignment-X and parent-alignment-X—IIRC, this was homogenised some a couple years ago. However, when wanting to adjust the alignment of a DynamicTextSpanner’s left bound, I found that this is much less clear for spanners. They have the parent-alignment-X component hidden behind the misleading property name attach-dir, and no default way of adjusting self-alignment-X via grob property (see this thread [1] for workarounds). I suggest modifying line-spanner-interface to use self-alignment-X and parent-alignment-X in all subproperties of bound-details, and heeding these properties for DynamicTextSpanner and similar grobs. Best, Simon [1] https://lists.gnu.org/archive/html/lilypond-user/2022-01/msg00389.html ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Wrong chord names in notation reference
Full agreement. Am 29.01.2022 um 21:14 schrieb skoop...@web.de: Hello, I noticed that a few chord names of the chord name chart in the notation reference (chapter A.1) are incorrect. These definitions are apparently derived from "Klaus Ignatzek: Die Jazzmethode für Klavier 1. Schott, 1995". I have this book in front of me and some chord names are not correct. Please compare the chord names there on page 18. 1) For example "c - e - g - d" is called "C add9" and not "C 9". Only if the 7 is included, you call it "C 7/9" or "C 9". 2) The same applies here: "c - e flat - g - f". The correct notation would be "Cm add11" or "Cm add4". "Cm 11" would be: "c - e flat - g - b flat - d - f" with 7 and 9. 3) "C lyd" and "C maj7 #11" mean the same thing, by the way. "c - e - g - b - f sharp" is appropriately called "Cmaj7 add#11". I know that there are different spellings for many chord symbols, but these mentioned points have actually been adopted incorrectly. I am not aware of any literature that justifies previous spellings. It would be great if these bugs were fixed soon. Many greetings ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond -- Johannes Feulner Tel: +49 721 66995492 johannes.feul...@scorio.com scorio WebMusic Bonhoefferweg 3 76327 Pfinztal Germany Inhaber Johannes Feulner ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
