Eemeli Aro
Eemeli Aro
Replying to @zbraniecki in https://github.com/unicode-org/message-format-wg/issues/28#issuecomment-1344276332: > > @eemeli: > > I continue to think that the shape of an MF2 formatted parts result should not be defined by the core...
@aphillips I've linked #541 to close this when it's merged.
The syntax proposed in this PR is now available here: https://github.com/unicode-org/message-format-wg/blob/experiments/experiments/markus/compromise-syntax.md
Closing the PR, as agreed at the last meeting.
@macchiati Would it be possible to move the resource WG repo under `unicode-org` in GitHub to more clearly note that this is something we're working on in parallel with but...
@aphillips It's outside the nominal scope of this issue and not yet covered by your comparison document, but you may want to look into prior art outside of MF1 to...
> It might be runtime dependent, for example a long and a short form of a message. The long form is best, as it is clear and does not use...
I think we've resolved this by selecting a variant selection method?
I believe that this was resolved by #368, which added this: https://github.com/unicode-org/message-format-wg/blob/7c080bfba867ec16abfc705e4ef5ed299a362e2e/spec/registry.dtd#L13
> I don't think that open/close/standalone are attributes of the function, they are attributes of the placeholder. I recognise that this is a current topic of conversation that's relevant, but...