Option to not include start and end section directives when exporting ChordPro

[Rdeblock]

These do not seem to provide any benefit. Instead of

{start_of_verse: Verse 1}
[|] [C] Who breaks the power [|] [%] of sin and darkness [|]
[|] [Fm7] Whose love is mighty [|] [%] and so much stronger [|]
[|] [Am] The King of glory [|] [G] the King above all k[|] [Fm7]ings [|] [NC] [|]
{end_of_verse}

...this displays the same in SongBookPro and MobileSheetsPro

{c: Verse 1}
[|] [C] Who breaks the power [|] [%] of sin and darkness [|]
[|] [Fm7] Whose love is mighty [|] [%] and so much stronger [|]
[|] [Am] The King of glory [|] [G] the King above all k[|] [Fm7]ings [|] [NC] [|]

It is cleaner. Some might prefer having the extra and some software might require it. So as an option would be great.

[no-chris]

hmmm potentially the current markup with start/end would help in some cases where the software automatically color codes verses/chorus/bridge?

[Rdeblock]

I can only speak for SongBookPro. It bases the color decision on the type of section. If it’s a verse, it uses whatever color I specified for verses, etc. It works fine after I’ve deleted the Start/end bits from the ChordPro source. MobileSheets doesn’t seem to allow coloring text other than with the textcolor, etc. directives. From: Christophe Noël ***@***.***> Sent: Thursday, November 7, 2024 12:47 PM To: no-chris/chord-chart-studio ***@***.***> Cc: Rdeblock ***@***.***>; Author ***@***.***> Subject: Re: [no-chris/chord-chart-studio] Option to not include start and end section directives when exporting ChordPro (Issue #658) hmmm potentially the current markup with start/end would help in some cases where the software automatically color codes verses/chorus/bridge? — Reply to this email directly, view it on GitHub<#658 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/BMRCZBVSDKTGU7XWCJGECGLZ7PGV3AVCNFSM6AAAAABRJ7XWPGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDINRTGE4DANRXGA>. You are receiving this because you authored the thread.Message ID: ***@***.***>