You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Essentially, we define the parameters to be added for a span tag, so there's no need to put span in the definition, but that gets added in translation.
Closing the user-defined tag, e.g. </bv> automatically translates to </span>, so no need to define that.
Could this be used to redefine existing convenience tags? Ideally, I think yes, but don't know what the implications are.
Custom tags won't make sense to third-party software (e.g. MSP), but that can be avoided by re-generating more compatible (but less readable) ChordPro files.
This could go within the pdf config section, or more general settings so it works with other output formats. I think the point above suggests is should be a general setting, so custom tags get expanded to full <span> tags for ChordPro output as well as PDF.
There may be overlap with more general discussion on custom styles (Custom styles #404), which seems a longer-term topic, but might be a consideration.
The text was updated successfully, but these errors were encountered:
As per user forum discussion
From a user point of view, an example might be defining
<bv>
for backing vocals and<hc>
for highlighted chord, used as:(I don't format chords ad hoc within songs, so not exactly sure whether markup should be fall inside or outside
[ ]
).Config could be as brief as:
Rationale/issues:
span
tag, so there's no need to putspan
in the definition, but that gets added in translation.</bv>
automatically translates to</span>
, so no need to define that.pdf
config section, or more generalsettings
so it works with other output formats. I think the point above suggests is should be a general setting, so custom tags get expanded to full<span>
tags for ChordPro output as well as PDF.The text was updated successfully, but these errors were encountered: