Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

US 2-029 3.35 [defns.multibyte] Give context for "execution character set" #474

Closed
wg21bot opened this issue Oct 30, 2022 · 4 comments · Fixed by cplusplus/draft#5910
Closed
Labels
Milestone

Comments

@wg21bot
Copy link
Collaborator

wg21bot commented Oct 30, 2022

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.

@wg21bot
Copy link
Collaborator Author

wg21bot commented Oct 30, 2022

The sugestion is to move this editorially to 16.3.3.3.5.3 Multibyte strings [multibyte.strings].

@jensmaurer jensmaurer added the editorial editorial label Oct 31, 2022
@jensmaurer
Copy link
Member

See cplusplus/draft#5910

@jensmaurer 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
@jensmaurer jensmaurer transferred this issue from another repository Nov 3, 2022
@jensmaurer
Copy link
Member

Accepted with Modifications.

The definition is used in subclause 16.3.3.3.5.3 [multibyte.strings] and was moved there.

@tahonermann tahonermann added the SG16 Unicode label Nov 3, 2022
@jensmaurer jensmaurer added this to the CD C++23 milestone Nov 3, 2022
@tahonermann
Copy link
Collaborator

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants