Hi Tom,

Some comments/requests.

For "can be broadly applied", can we clarify by adding "(and thus should
only be used when a broad interpretation is actually intended)".

For:
Hubert pointed out a category error in the proposed wording change for the
codecvt facets; "code point" is used where "code unit" would be more
appropriate.

the description of the category error that was raised should be something
like:
"the first bullet is a description of the artifacts produced by an
encoding, not of an encoding itself; the second bullet names an encoding:
both bullets should be written such that they can be easily read as
specifying encodings"

Thanks,


Hubert Tong

On Sun, Jan 15, 2023 at 4:43 PM Tom Honermann via SG16 <
sg16_at_[hidden]> wrote:

> The summary for the SG16 meeting held January 11th, 2023 is now
> available. For those that attended, please review and suggest corrections.
>
> - https://github.com/sg16-unicode/sg16-meetings/#january-11th-2023
>
> No decisions were made at this meeting.
>
> Tom.
>
> --
> SG16 mailing list
> SG16_at_[hidden]
> https://lists.isocpp.org/mailman/listinfo.cgi/sg16
>