Re: [I18ndir] [art] Fwd: New Version Notification for draft-bray-unichars-06.txt

Hi,

> It cannot be serialized into well-formed UTF-8, but the behavior of
libraries
> asked to parse the sample is unpredictable; some will silently parse this
> and generate an ill-formed UTF-8 string.

It might be better to say "Its code points do not represent well-formed
UTF-8..." (or well-formed Unicode?), because the example does show it
serialized as well-formed UTF-8 via escape sequences. Not attached to my
suggestion, but the current text is a little confusing.

> Reasonable options for dealing with problematic input include, first,
rejecting text
> containing problematic code points, and second, replacing them with
placeholders.
> Silently ignoring an ill-formed part of a string is a known security
risk. Responding
> to that risk, [UNICODE
<https://www.ietf.org/archive/id/draft-bray-unichars-06.html#UNICODE>] section
3.2 recommends dealing with ill-formed byte
> sequences by by signaling an error, or replacing problematic code points
with
> "�" (U+FFFD, REPLACEMENT CHARACTER).

typo: "by by"

I'll try a suggestion:

"There are reasonable options for dealing with problematic input. First, an
implementation
can reject text containing problematic input. Secondly, it's possible to
replace problematic
code points with placeholders.  Responding to that risk, [UNICODE
<https://www.ietf.org/archive/id/draft-bray-unichars-06.html#UNICODE>] section
3.2 recommends
dealing with ill-formed byte sequences by signaling an error, or replacing
problematic code points with '�' (U+FFFD, REPLACEMENT CHARACTER). Lastly,
it can make sense to accept it, if the entire implementation
is designed to accommodate ill-formed Unicode."

Not attached to my words, just trying to get the point across.

thanks,
Rob

On Mon, Sep 25, 2023 at 9:51 AM Tim Bray <tbray@textuality.com> wrote:

> What’s new and different here.
>
>
>    1. Locked down definition of “problematic”
>    2. Locked down definition of “character repertoire”
>    3. Changed “Useful Assignables” to “Unicode Assignables” (checked with
>    Asmus first)
>
>
> A new version of Internet-Draft draft-bray-unichars-06.txt has been
> successfully submitted by Paul Hoffman and posted to the
> IETF repository.
>
> Name:     draft-bray-unichars
> Revision: 06
> Title:    Unicode Character Repertoire Subsets
> Date:     2023-09-25
> Group:    Individual Submission
> Pages:    10
> URL:      https://www.ietf.org/archive/id/draft-bray-unichars-06.txt
> Status:   https://datatracker.ietf.org/doc/draft-bray-unichars/
> HTML:     https://www.ietf.org/archive/id/draft-bray-unichars-06.html
> HTMLized: https://datatracker.ietf.org/doc/html/draft-bray-unichars
> Diff:     https://author-tools.ietf.org/iddiff?url2=draft-bray-unichars-06
>
> Abstract:
>
>   This document discusses specifying subsets of the Unicode character
>   repertoire for use in protocols and data formats.
>
>
>
> The IETF Secretariat
>
>
> _______________________________________________
> art mailing list
> art@ietf.org
> https://www.ietf.org/mailman/listinfo/art
>