-
Notifications
You must be signed in to change notification settings - Fork 4
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
FR-020-014 5.3 [lex.charset] Replace "translation character set" by "Unicode" P2749 #422
Comments
SG16 discussed this issue during its 2022-12-14 telecon. The following poll was taken:
We still lack proposed wording to address this issue. I am retaining the SG16 label pending a wording proposal. If such a proposal does not materialize or we are unable to review it in time, then this NB comment will need to be resolved as having no consensus for a change. |
A draft paper is available to address this issue, but it has not been published in a mailing yet. D2749R0 (Down with ”character”). |
SG16 reviewed a draft of what will become P2749R0 (Down with ”character”) during its 2023-01-25 telecon but has not yet polled forwarding it. That paper seeks to resolve this NB comment. SG16 will continue its review on 2023-02-01. I'm retaining the SG16 label for now. |
SG16 continued its review of what will become P2749R0 (Down with ”character”) during its 2023-02-01 telecon. The following polls were taken.
Though there was no consensus to forward the paper for C++23, there is strong support to continue work on the paper for a later standard; the rejection at this point has to do with a desire for further review and a desire to expand the scope of the paper to avoid introducing inconsistencies in core wording. I'm removing the SG16 label; this NB comment is ready for CWG review. |
Rejected. There was no consensus for a change at this time. |
C++23 introduces the term "translation character set" to designate Unicode scalar values.
This new term is C++ specific and has no benefit over the terms scalar value or codepoints (both can be used interchangeably as surrogates are not permitted after phase 1 of translation).
Because other terms exist, and because making characters up for non-assigned codepoints doesn't match any possible definition of the term "character", we would like to the term "translation character set" replaced by "Unicode" and "elements of the translation character set" replaced by codepoint or scalar value. In places in [lex] where the term character is used to mean "codepoint", it should be replaced by "codepoint".
The text was updated successfully, but these errors were encountered: