Conversation
…f <unit mf:select> & <segment id>
Great!
I'm trying to understand this one. Why does the "identifier of the default case" need to be retained, at least for plurals, when "other" is always the default case? Or are there situations where Maybe answering my own question: Are you trying to preserve the distinction between What about preserving the non-compliant |
srl295
left a comment
There was a problem hiding this comment.
Looks good though a question about *:other
@srl295 While the MF2 syntax does not support default case labels, the data model does. It's mostly there to support MF2 being used to represent other syntaxes that do support such labels, like Fluent. The feature itself has a couple of use cases:
For plurals in particular, it's also good to be able to avoid For Xliff I think we do want to present some textual label here, as we should not presume that either the translator or the tooling working with the file will have any understanding or familiarity with MF2 or its syntax.
Yeah, defaulting to just |
Fixes #456
This adopts the attributes introduced in the Plural, Gender, and Select Module that was added in Xliff 2.2 rather than the
<unit mf:select>and<segment id>attributes.The
pgs:casevalues use a*:prefix for the default case, as in*:otheror*:nominative. This is a deliberate difference from the Xliff spec's recommendation, to allow for the identifier of the default case to be retained.CC @srl295, @catamorphism