David Kastrup <d...@gnu.org> writes: > David Kastrup <d...@gnu.org> writes: > >> Simon Albrecht <simon.albre...@mail.de> writes: >> >>> Am 20.06.2015 um 00:27 schrieb MarcM: >>>> is this collision a bug or is it expected and require to add padding >>>> manually? >>> You might call it a bug, but of course it’s not a bug of Lilypond but >>> a bug in the \startParenthesis and \stopParenthesis variables defined >>> here. >> >> In that case, there are no bugs in LilyPond: every other behavior is >> also a consequence of the code in LilyPond. >> >> At any rate, it is issue 155 >> <URL:https://code.google.com/p/lilypond/issues/detail?id=155> and has >> been fixed in version 2.19.20. > > Sorry for the confusion: I did not realise that this wasn't part of > LilyPond. At any rate, the code (and properties) defined in issue 155 > might help for refining the respective > \startParenthesis/\stopParenthesis code to take accidentals in account.
Aaaaand it turns out that no redefinition is necessary. This code produces proper parentheses without overlap perfectly well right now. So just upgrade to 2.19.20 or newer. -- David Kastrup _______________________________________________ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
