On 1/22/20 2:56 AM, Corentin Jabot via SG16 wrote:
> XID_Continue and XID_Start are, in fact, stable
> https://unicode.org/policies/stability_policy.html

Can you elaborate? My reading of the stability policy is that once a
character has the XID_Start or XID_Continue property that it always
will, but that policy doesn't state that (existing or new) characters
that don't have those properties can't be granted them in the future.

Tom.

>
> On Wed, 22 Jan 2020 at 06:23, Tom Honermann via SG16
> <sg16_at_[hidden] <mailto:sg16_at_[hidden]>> wrote:
>
> The summary for the SG16 meeting held January 8th, 2020 is now
> available. For those that attended, please review and suggest
> corrections:
> - https://github.com/sg16-unicode/sg16-meetings#january-8th-2020
>
> The next meeting is scheduled for Wednesday, January 22nd, from
> 3:30-5:00pm EST. An invitation (from invite_at_[hidden]
> <mailto:invite_at_[hidden]>) has been sent to the mailing list
> and prior attendees. The draft agenda is:
> - P1885R0: Naming Text Encodings to Demystify Them
> <https://wg21.link/p1885>
> - Follow up on recent mailing list discussions.
> - Identify and discuss intended use cases.
> - P2020R0: Locales, Encodings and Unicode <https://wg21.link/p2020>
> - General discussion, corrections, suggestions, etc...
>
> For any new attendees: The meetings are video conferences
> conducted via BlueJeans. If you are planning to attend, please
> test your system by visiting https://bluejeans.com/111 before the
> scheduled meeting time.
>
> Tom.
>
> --
> SG16 mailing list
> SG16_at_[hidden] <mailto:SG16_at_[hidden]>
> https://lists.isocpp.org/mailman/listinfo.cgi/sg16
>
>