[I18ndir] Fwd: New Version Notification for draft-bray-unichars-04.txt

[Tim Bray <[e-mail]>]

 Hello again.  This draft corrects errors pointed out on these mailing
lists (thanks!) and goes to some length to address the arguments that
mentioning the All-Code-Points option is toxic, and that the definition of
UTF-8 excludes the possibility of surrogates. It relies more strongly on
the discussions in RFC 9413 (which BTW I hadn’t read except in an early
draft - I recommend to everyone, it’s really good).

Comments are specifically requested about the desirability of advancing
this document in the IETF.  I think it would be better if such comments
avoid discussing the history of the JSON specifications - it really, really
doesn’t matter now, they are what they are.
==================

A new version of Internet-Draft draft-bray-unichars-04.txt has been
successfully submitted by Paul Hoffman and posted to the
IETF repository.

Name:     draft-bray-unichars
Revision: 04
Title:    Specifying Unicode Character Repertoires in RFCs
Date:     2023-09-15
Group:    Individual Submission
Pages:    11
URL:      https://www.ietf.org/archive/id/draft-bray-unichars-04.txt
Status:   https://datatracker.ietf.org/doc/draft-bray-unichars/
HTML:     https://www.ietf.org/archive/id/draft-bray-unichars-04.html
HTMLized: https://datatracker.ietf.org/doc/html/draft-bray-unichars
Diff:     https://author-tools.ietf.org/iddiff?url2=draft-bray-unichars-04

Abstract:

  This document describes four subsets of Unicode characters and their
  use in protocols and data formats.



The IETF Secretariat