[FEEDBACK] Use of | in markup

[macchiati]

{#button}Submit{/button} or {#img alt=|Cancel| /}.

This is misleading. Someone might think that the |​ characters are corresponding to ' or " when they don't really represent that, or think they are needed when they are not. Recommend removing the | characters or adding a note.

[aphillips]

Not sure I understand? Markup is subject to our syntax:

markup = "{" o "#" identifier *(s option) *(s attribute) o ["/"] "}"  ; open and standalone
       / "{" o "/" identifier *(s option) *(s attribute) o "}"  ; close

... and thus you have to use quoted (or unquoted) literals for option values. Do not mistake thinking that {#img} is an HTML tag 😉

[macchiati]

That is, we can write this in two ways, because the word Cancel doesn't contain spaces (etc), it doesn't need |...|

{#button}Submit{/button} or {#img alt=|Cancel| /}

or

{#button}Submit{/button} or {#img alt=Cancel /}

When we put | in where it isn't needed it can mislead readers into thinking that because html uses <img alt="Cancel">, MF needs the | in place of ". (We have seen cases where people are confused into thinking that | works like ", when it doesn't.)

[eemeli]

We have seen cases where people are confused into thinking that | works like ", when it doesn't.

Maybe I'm confused as well, because I also think that for MF2 | does work like " elsewhere? This is similar to HTML, which will parse both <img alt=Cancel> and <img alt="Cancel"> with the same meaning.

[aphillips]

@macchiati Moving to 48 because this doesn't feel material to 47. Note that I have proposed as a resolved-candidate

[macchiati]

Makes sense.