A comment on @aphillips's suggestion:

or in syntaxes used by various programming and scripting languages.

It isn't just that vertical pipes are rare in other syntaxes, but specifically that they are rare as quote delimiters.

' and " are not special to us, so we can lump these in with other characters that we also rejected while searching for characters that are not common in natural language or programming syntax to use as a quote character.

Example

{"Quoted \"literal\""}

when embedded into (say) a JSON file might require the developer to type:

"message": "{\"Quoted \\\"literal\\\"\"}"

Make sense?

When our escape and quote characters conflict with those of the host syntax,
this would require the user to escape our quotes
and to double-escape our quoted quotes.

This is why #414 suggests allowing either ' or " as quoted delimiters. That way, your example could be expressed as

{'Quoted "literal"'}

and be embedded in JSON as

"message": "{'Quoted \"literal\"'}"

so only the " that are actual characters of the literal need to be quoted, exactly as is the case with |.

Hence our explanation ought to say why the above is a worse option than picking a novel quote delimiter |. This is missing from your suggestion.

That works in JSON, but not in many syntaxes (which are more rigid about quotes). And the quote alternation can depend on the exterior quoting regime not visible to e.g. translation tooling. Changes to the quote characters look like differences to processes such as translation memory.

It might be helpful to just embed something like that example, e.g.

For example, message = '{|Eat At Joe\'s|}' (using | as the MessageFormat quote delimiter and using the embedding language's syntax to include a literal ' in a '-delimited string containing the message) is more readable than the alternative message = '{\'Eat At Joe\\\'s\'}' (using ' as the MessageFormat quote delimiter, which must itself be escaped in the embedding language along with both characters of the \' MessageFormat-level sequence for including a raw ' in a '-quoted literal).

That works in JSON, but not in many syntaxes (which are more rigid about quotes).

Could you give an example? I'm not sure how a resource syntax could be more rigid about quotes than JSON.

And the quote alternation can depend on the exterior quoting regime not visible to e.g. translation tooling. Changes to the quote characters look like differences to processes such as translation memory.

Sure, if you're comparing the exact string representations of messages. However, a reasonable MF2 message comparator would either compare the data model representations of messages, or their understanding of each message's canonical source strings, which would normalise away any whitespace or quotation style differences.

There are 2 conveniences that | give us:

1. "inwards", it's easy to include " and ' in literals, without escaping them via \,
2. "outwards", it's easy to embed messages with string literals in code or container formats.

The combination of these two is particularly interesting: it's when a message both contains quotes in literals and is embedded in code. If we delimited literals with " or ', then we'd often need to solve two problems at the same time:

• escape quotes inside literals via \, and
• escape quotes delimiting literals in code or container formats and escape the MF2's \ from the bullet above, because it's a common escape char in many languages.

This is how we get the gnarly \\\. By using |, we sidestep both problems.