</marker> is actually invalid, and must be rejected as an error because
tolerating it imparts a false meaning to a file that has it. This is the
exact reason using an entirely different syntax is on the table, so that
people are not tempted to do invalid things like that.
Henry
On May 30, 2016 12:55:02 PM Zhang Michael <[email protected]> wrote:
I'm in favor of option 1 <marker> except that I think </marker> can be
tolerated as kind of "retrograded" but valid syntax, and it is simply
ignored by the parser.
Thanks,
Michael
________________________________________
发件人: Gregorio-users <[email protected]> 代表 Henry So Jr.
<[email protected]>
发送时间: 2016年5月30日 20:37
收件人: [email protected]
主题: [Gregorio-users] Gabc syntax for "markers"
Dear all,
The developers are working on a couple of features that will require
"markers" to be placed in syllable text.
For context, see
https://github.com/gregorio-project/gregorio/issues/1029
and
https://github.com/gregorio-project/gregorio/issues/931.
These two features will require some kind of "marker" to be placed in
gabc, but unlike the current tags (like <b>...</b>), these "markers"
don't need to (and should not) be closed.
The developers are at an impasse as to the best notation for this.
There are three options:
- <marker> (with no (</marker>), which may confuse people used to XML)
- <marker/> (this is XML-like, but may be hard to remember)
- $marker$ (which makes it obvious this is different, but is different)
Does anyone on the list have an opinion on which form they find least
confusing/difficult-to-use?
Thanks,
Henry
_______________________________________________
Gregorio-users mailing list
[email protected]
https://mail.gna.org/listinfo/gregorio-users
_______________________________________________
Gregorio-users mailing list
[email protected]
https://mail.gna.org/listinfo/gregorio-users
