[albatros]

Since the manual is unfortunately not up to date - I know that this is a lot of work that is no fun - the question:
Is there a complete list of all {} directives that are evaluated by MSP?
(It was only by chance that I found out, for example, that {meta SongID} can be used).

thank you

[Zubersoft]

I'm just going to grab some excerpts from code (some of these are for the upcoming update such as ABC support):

"title", TITLE
"t", TITLE
"subtitle", SUBTITLE
"st", SUBTITLE
"su", SUBTITLE
"album", ALBUM
"a", ALBUM
"artist", ARTIST
"composer", COMPOSER
"year", YEAR
"key", KEY
"capo", CAPO
"tempo", TEMPO
"time", TIME_SIG
"duration", DURATION
"comment", COMMENT
"c", COMMENT
"guitar_comment", COMMENT
"gc", COMMENT
"start_of_chorus", START_OF_CHORUS
"soc", START_OF_CHORUS
"end_of_chorus", END_OF_CHORUS
"eoc", END_OF_CHORUS
"start_of_tab", START_OF_TAB
"sot", START_OF_TAB
"end_of_tab", END_OF_TAB
"eot", END_OF_TAB
"define", CUSTOM_CHORD
"chord", CUSTOM_CHORD
"copyright", COPYRIGHT
"footer", FOOTER
"book", BOOK
"textsize", TEXT_SIZE
"textfont", TEXT_FONT
"chordsize", CHORD_SIZE
"chordfont", CHORD_FONT
"highlight", HIGHLIGHT
"comment_italic", HIGHLIGHT
"ci", HIGHLIGHT
"chorus", REPEAT_CHORUS
"new_page", PAGE_BREAK
"np", PAGE_BREAK
"tabsize", TAB_SIZE
"chorussize", CHORUS_SIZE
"comment_box", COMMENT_BOX
"cb", COMMENT_BOX_OR_BREAK
"meta", META
"column_break", COLUMN_BREAK
"transpose", TRANSPOSE
"start_of_part", START_OF_PART
"sop", START_OF_PART
"end_of_part", END_OF_PART
"eop", END_OF_PART
"start_of_bridge", START_OF_PART
"sob", START_OF_PART
"end_of_bridge", END_OF_PART
"eob", END_OF_PART
"start_of_verse", START_OF_VERSE
"sov", START_OF_VERSE
"end_of_verse", END_OF_VERSE
"eov", END_OF_VERSE
"start_of_grid", START_OF_GRID
"sog", START_OF_GRID
"end_of_grid", END_OF_GRID
"eog", END_OF_GRID
"start_of_abc", START_OF_ABC
"soa", START_OF_ABC
"end_of_abc", END_OF_ABC
"eoa", END_OF_ABC

For meta fields, I support notation [src] [[display]] as well as the following:

id
songid
sorttitle
collection
setlist
source
genre
difficulty
custom
custom2
customgroup
keywords
rating

Mike

[albatros]

Thank you.

Are {chord} and {define} already implemented? If so, can you give a short example of their use?

[Zubersoft]

No, that's coming with the next update. I'm going to try to follow the specification as much as possible:

https://www.chordpro.org/chordpro/directives-chord/
https://www.chordpro.org/chordpro/directives-define/

Mike

[Andrew9999]

If I want to make chords Bold, I can do this explicitly via MobileSheets - but only for that song, and not as part of the ChordPro text.  Is there a way to do this with e.g. {ChordFont:xxx}?  Thanks.

[Zubersoft]

At the moment, no, as I don't support that directive.

Mike

[itsme]

@Andrew9999:
" If I want to make chords Bold, ..."
MobileSheets supports many Pango formatting options. Pango also works for chords, you just have to write the Pango directives within the square brackets.
Here's one of my test files from the time when Pango was newly introduced in ChordPro. Sorry, it's German and some statements might be a bit outdated. Hope it helps anyway, just import it into MobileSheets and take a look.