Consider renaming the "compatibility" bidi isolation strategy
eemeli opened this issue · comments
Eemeli Aro commented
As identified by @aphillips in tc39/proposal-intl-messageformat#30 (comment):
compatibility
sounds like it exists for legacy reasons rather than wanting to be the default options. Perhaps give it a less redolent name, likeunicode
orcontrols
?
As this name is coming from our spec, here, we should apply any such name change to the MF2 spec.
Addison Phillips commented
The name "compatibility" is not formally defined for the required bidi isolation strategy. We should name it formally in the document so that it can be linked to. I will probably have other comments about it. After we merge the reformulation, I will take this issue and make a PR.