RE: UAX44: loose matching of symbolic values and the `is` prefix

Mathias Bynens wrote: >> Rather than changing the spec based on anecdotal evidence, [...] >> >> It seems irresponsible to assume now that nobody anywhere needs >> it. > > What assumption are you talking about? Markus and Nova provided actual > examples of implementations not following the spec,

Re: UAX44: loose matching of symbolic values and the `is` prefix

> On 7 Jun 2016, at 17:56, Doug Ewell wrote: > > Rather than changing the spec based on anecdotal evidence, […] > > It seems irresponsible to assume now that nobody anywhere needs > it. What assumption are you talking about? Markus and Nova provided actual examples of

Re: UAX44: loose matching of symbolic values and the `is` prefix

Mathias Bynens replied to Nova Patch: >> [...] Based on my past research for Unicode Regular Expression >> Engines at IUC38, I suspect that there might not be any regex engine >> that actually supports syntax like Script=IsGreek as described in >> UAX44-LM3! If anybody knows otherwise, I’d love

Re: UAX44: loose matching of symbolic values and the `is` prefix

> On 7 Jun 2016, at 00:39, Nova Patch wrote: > > […] Based on my past research for Unicode Regular Expression Engines at > IUC38, I suspect that there might not be any regex engine that actually > supports syntax like Script=IsGreek as described in UAX44-LM3! If anybody

Re: UAX44: loose matching of symbolic values and the `is` prefix

Den mandag 6. juni 2016 skrev Doug Ewell følgende: > > Mathias Bynens wrote: > > > The `is` prefix doesn’t provide any functionality that would otherwise > > be unavailable. It doesn’t add any value, yet causes incompatibility, > > author confusion, and it increases implementation complexity. > >

Re: UAX44: loose matching of symbolic values and the `is` prefix

On 6/6/2016 9:09 AM, Markus Scherer wrote: Interesting discussion! ICU does not support "is" nor "in" prefixes. I wasn't even aware that UAX #44 loose matching prescribes "is". ICU just implements what

Re: UAX44: loose matching of symbolic values and the `is` prefix

Interesting discussion! ICU does not support "is" nor "in" prefixes. I wasn't even aware that UAX #44 loose matching prescribes "is". ICU just implements what Property[Value]Aliases.txt say: # Loose matching should be applied to all property names and property values, with # the exception of

Re: UAX44: loose matching of symbolic values and the `is` prefix

> >> The `is` prefix doesn’t provide any functionality that would otherwise >> be unavailable. It doesn’t add any value, yet causes incompatibility, >> author confusion, and it increases implementation complexity. > > I don't see any evidence that it adds no value. Support for existing >

Re: UAX44: loose matching of symbolic values and the `is` prefix

> On 6 Jun 2016, at 18:04, Ken Whistler wrote: > > UAX #44 doesn't *require* any regex engine to include this "is prefix" > handling. Are you referring to the fact that the first paragraph on http://unicode.org/reports/tr44/#Matching_Rules uses “strongly recommended”

Re: UAX44: loose matching of symbolic values and the `is` prefix

Mathias Bynens wrote: > Looking at implementations in the wild, Steven Levithan found > (https://github.com/mathiasbynens/es-unicode-regexp-proposal/issues/2#issuecomment-143288062) > that some regex flavors use `Is` for scripts, some for blocks, some > for scripts and blocks, some for neither.

Re: UAX44: loose matching of symbolic values and the `is` prefix

On 6/6/2016 12:58 AM, Mathias Bynens wrote: Backwards compatibility seems to be the only good reason to continue supporting the `is` prefix*for existing implementations*, such as the one in Perl. But why is it still a requirement for new engines to support it as part of UAX44-LM3? I’d like

Re: UAX44: loose matching of symbolic values and the `is` prefix

Thanks Ashley. > > On 06 June 2016 at 08:58 Mathias Bynens wrote: > > > http://unicode.org/reports/tr44/#UAX44-LM3 mentions the `is` prefix: > > > For loose matching of symbolic values, an initial prefix string "is" is > > ignored. […] Ignoring any initial

UAX44: loose matching of symbolic values and the `is` prefix

http://unicode.org/reports/tr44/#UAX44-LM3 mentions the `is` prefix: > For loose matching of symbolic values, an initial prefix string "is" is > ignored. […] Ignoring any initial "is" on a symbolic value during loose > matching is likely to produce the best results in application areas such as