The normative references in the spec are all pointing to line-break classes defined in UAX14 to which a particular behaviour in the spec should be assigned. There's still no statement in the spec (other than a note which simply says that further information can be found for all scripts in UAX14) that says that **in the absence of** other rules, then the UAX14 line-breaks should be applied as a fallback. Having this in the spec will promote interoperability in the cases not called out, and will encourage implementers to fully implement UAX14 for the non-controversial cases that are currently outstanding. I think we should raise a GH issue to give this visibility. -- GitHub Notification of comment by r12a Please view or discuss this issue at https://github.com/w3c/i18n-activity/issues/91#issuecomment-628578641 using your GitHub accountReceived on Thursday, 14 May 2020 11:43:26 UTC
This archive was generated by hypermail 2.4.0 : Monday, 4 July 2022 18:09:42 UTC