On 06/19/2016 07:25 AM, Daniel Bünzli wrote:
> Le dimanche, 12 juin 2016 à 14:26, Daniel Bünzli a écrit :
>> Hello,
>>
>> I notice that in 9.0.0, UAX29 segmentations no longer report boundaries on the empty string while UAX14 still does report a hard line break on it. Is this intended ? and what is the rationale behind these changes and non-changes ?
>>
>> While I think that the proposed UAX29 is a better one, these kind of changes on special cases make it easy to break assumptions made by client code so it would be better if these things do not change to often. Hence my request, shouldn't UAX14 also report no breaks on the empty string ?
> I realize we are out of the beta review time. But do people think it would be worth raising for 10.0.0 ?
>
> Best,
>
> Daniel
>
>
Yes. Use http://www.unicode.org/reporting.html to make an error report.
I did this last year to report about the empty strings matching, and
TR29 got changed for 9.0. (Perhaps others reported it too.) I was
aware that the problem was also in TR14, but I don't remember now, I
could very well have not included this in my submission. And the
Unicode personnel are busy people, and like me, can overlook things, and
fail to draw logical inferences that, in retrospect, appear to be obvious.
Received on Sun Jun 19 2016 - 10:59:07 CDT
This archive was generated by hypermail 2.2.0 : Sun Jun 19 2016 - 10:59:08 CDT