You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The notion of an "execution character set" is no longer given prominence in the Draft standard, aside from some notes about its relationship to the concept as defined by C, and clarifying that certain character encodings are unrelated to this character set. This makes it a questionable choice for use in the definition of "multibyte character".
Proposed change:
Change the definition of "multibyte character" to use a character encoding with a more definite specification given by the Standard.
The text was updated successfully, but these errors were encountered:
jensmaurer
changed the title
US 3.35 [defns.multibyte] Give context for "execution character set"
US 2-029 3.35 [defns.multibyte] Give context for "execution character set"
Nov 3, 2022
This issue has already been resolved. The following describes events that contributed to its resolution.
SG16 reviewed this NB comment during its 2022-10-19 telecon. The following poll was taken:
Poll 1: [US 2-029] SG16 suggests to consider this issue as "not a defect", but to improve
the presentation by editorially moving the definition of "multibyte character" to [multibyte.strings].
Attendees: 8
No objection to unanimous consent.
The (editorial) changes made are consistent with the polled SG16 direction.
The notion of an "execution character set" is no longer given prominence in the Draft standard, aside from some notes about its relationship to the concept as defined by C, and clarifying that certain character encodings are unrelated to this character set. This makes it a questionable choice for use in the definition of "multibyte character".
Proposed change:
Change the definition of "multibyte character" to use a character encoding with a more definite specification given by the Standard.
The text was updated successfully, but these errors were encountered: