eemeli
commented
1 year ago Some examples:
# Example message resource
# This first two-line comment attaches to the whole resource
key = {value}
some.greeting = {Hello {$place}!}
kääk\ \&\ yök = {Message with key "kääk & yök"}
multiline = {This message
consists of three lines,
\ and this line starts with two spaces.}
[section]
# This is a standalone comment.
# This comment attaches to the with-vars message.
with-vars =
let $foo = {$bar :number}
{The count is {$foo}}
with-variants =
let $foo = {$bar :number}
match {$foo}
when one {You have {$foo} thing.}
when * {You have {$foo} things.}
# This comment attaches to the section.sub section
[section.sub]
key = {Inner message at section.sub.key}
key . sub.key = {Message at section.sub.key.sub.key}
flodolo
Closes #8, and presents initial answers for other issues, to which I'll add relevant comments.
An initial ABNF (RFC 5234, RFC 7405) syntax for a resource format is added, to act as a starting point.
The format is closely related to TOML and other
.ini-like formats, as discussed in #8. Compared to what's presented there, the only real divergence is that"quoted keys"are left out, and instead\escape sequences are well defined for both keys and values. This allows for any non-empty string to be used as a either a key or a value, and ensures that a resource is made up only of printable characters.A key feature of the syntax is that multiline values are the only indented content in the syntax, and in value will have all of their leading whitespace stripped. This allows for a rather clean separation between message and resource syntaxes, so that a single file could be parsed by either a single-pass or multi-pass parser. The cost of this choice is that messages that contain lines after the first with leading whitespace (i.e. would match the regexp
/\n[ \t]/need to add a\escape before the first contentful whitespace on the line.