Meeting Agenda : 2022-04-11 (Recoverability)

[eemeli]

Unicode MessageFormat WG - Weekly Meeting

Time: 18:30 CEST - 9:30 PDT

Call : Link

Notes: Link

This weekly meeting will focus on recoverability in syntax parsing, with an introduction by @zbraniecki. Related concepts to this have previously been touched on in issue #45. A brief explanation from Zibi, cribbed from elsewhere:

Syntax of a single message gates ability of a resource syntax to handle “bail from a broken message, find the beginning of a next one, continue” - esp consideration of multi-line message content, or multi-line selectors.

• Fluent uses “new line + [a-z#-] indicates a new entry (message, term or comment)”. Multi-line and SelectExpression can’t use that.
• How does an unclosed placeholder “end” if it is not closed? Will it “swallow” till EOF? What can we establish as a fallback terminator? Same for string literal.

Generally, for MF2.0 resource spec for the Web, we’d like to encourage “fuzzing” - randomly replace characters in a message, or cut a message at arbitrary character, and maximize situations where the parser can identify an error and find the start of the next message.