Oh, I just tested and

Command: Parenthesize Chord (Off/On)
Enclose the chord in ( ) on printing.
Location: Object Menu ▶ Chords
Internal Name: ParenthesizeChord


does what you want for a single chord. But, at least with LilyPond
version 2.24 there is a bug preventing its sister commands which do an
open or a close paren on their own from working - the syntax seems to
have changed ... (see Object Menu ▶ Chords menu for these - they should
work in earlier LilyPond versions)

Richard


On Mon, 2024-11-04 at 08:47 +0000, Richard Shann wrote:
> On Mon, 2024-11-04 at 02:51 +0000, wak...@tilde.team wrote:
> > hello all,
> > 
> > First time posting to the list, I've used Denemo for a couple of
> > scores now and I really enjoy it. I'm hoping someone can 
> > advise me on how to add parenthesis around chord names above the
> > staff, this is a common mark at the end of jazz lead sheets. 
> > For example, I want to typeset (G-7 C-7 F7) parens included
> 
> One way to do this would be to use the fact that you can customise
> chord symbols - so you could make a set of chord symbols that are the
> usual chord symbol but with an open parenthesis before it and another
> set that did things like C-7) ...
> I'll remind myself how you customise chord symbols in Denemo and come
> back to you on this. However,
> 
> >  above the staff over three measures.
> > I've searched Denemo and Lilypond docs 
> 
> that's a rather kludgy way to go, asking on
> lilypond-u...@gnu.org will
> undoubtedly give you some neat syntax to use, and armed with that you
> could come back to this list if it wasn't obvious how to insert said
> syntax into a Denemo score.
> 
> > [...]
> > I tried inserting a text mark above the staff, and that prints the
> > paren in the print view, but I can't drag the paren to 
> > position it properly (even if I click on typeset in the print view
> > --
> > maybe I'm doing it wrong). The little hand cursor shows 
> > up, but nothing happens when I click on the paren.
> 
> Can you drag *any* text marks? 
> 
> Richard
> 
> > 
> > Thanks for any help, George
> > 
> 
> 


Reply via email to