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.

Sign up for GitHub

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

Jump to bottom

[format.string.std] Should "UCS" be replaced with "Unicode"? #6155

Closed
JohelEGP opened this issue Feb 28, 2023 · 2 comments
Closed

[format.string.std] Should "UCS" be replaced with "Unicode"? #6155

JohelEGP opened this issue Feb 28, 2023 · 2 comments

Comments

@JohelEGP
Copy link
Contributor

JohelEGP commented Feb 28, 2023 •
edited

#6144 adds a new use of "UCS scalar value". #6126 changed all occurrences of it to "Unicode scalar value". Should this added "UCS" also be changed to "Unicode"?

#6144 also adds some uses of "Unicode encoding". Although #6126 changed many of those, it left some (reproduced below), so perhaps the added ones can stay.

$ git checkout motions-2023-02-cwg-8
$ git grep 'Unicode encoding' *.tex
future.tex:  arguments for these functions. How Unicode encoding conversions are performed is
lex.tex:for the respective Unicode encoding form.
lex.tex:No character lacks representation in any Unicode encoding form.
time.tex:If the string literal encoding is a Unicode encoding form and
@JohelEGP JohelEGP mentioned this issue Feb 28, 2023
Merged
@jensmaurer
Copy link
Member

Yes to the first.

The second needs further inspection.

"No character lacks representation in any Unicode encoding form." is a true statement for any Unicode encoding form (also those beyond UTF-8,16,32).

burblebee added a commit that referenced this issue Mar 1, 2023
@burblebee
[format.string] Apply Unicode fixes as per P2736R2 to wording added i…
d721879 
…n P2572R1

Partially fixes #6155.
@JohelEGP
Copy link
Contributor Author

JohelEGP commented Apr 1, 2023

Resolved by #6144 itself.

@JohelEGP JohelEGP closed this as completed Apr 1, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@JohelEGP @jensmaurer