<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<div class="moz-cite-prefix">On 7/14/19 10:28 PM, Philip Ridout
wrote:<br>
</div>
<blockquote type="cite"
cite="mid:CAG20JED+Pof-_TZJy8J=THNOgOkSxccf67QiJ_AK1AK3e9b75A@mail.gmail.com">
<meta http-equiv="content-type" content="text/html; charset=UTF-8">
<div dir="ltr">About a month ago I came up against an issue to do
with the way we handle chords. The issue was that a user who I
was importing songs for used "[x/y]" to denote the current verse
/ total verses and the fact that we use the chord pro format
(which also uses square brackets), meaning that you cannot use
square brackets and chords in the same song.</div>
</blockquote>
chordpro is more or less an industry standard. I think we should
stick with it.<br>
<blockquote type="cite"
cite="mid:CAG20JED+Pof-_TZJy8J=THNOgOkSxccf67QiJ_AK1AK3e9b75A@mail.gmail.com">
<div dir="ltr">
<div><br>
</div>
<div>I've been thinking about this, instead of the chord pro
format, I think we should use the method supported by
OpenLyrics, that is a chords xml tag. This should free up
square brackets to be used however they feel fit. Which begs
the question how should the user enter tags in the song
editor. I think I have come up with a solution. We use web
view and contenteditable. I have created some rather rough
sample code (<a href="https://jsfiddle.net/c8k31sp4/"
moz-do-not-send="true">htps://jsfiddle.net/c8k31sp4/</a>).</div>
</div>
</blockquote>
My personal opinon of xml is, that it's not very user friendly.
Instead I guess we should add (if not already there) the option to
escape square brackets using "\"<br>
</body>
</html>