UTFn->UTF-n

[danmoseley]

It's my understanding from https://www.unicode.org/reports/tr17 that the hyphen form is correct. So make strings and doc comments consistent.

[ghost]

Tagging subscribers to this area: @dotnet/area-meta
See info in area-owners.md if you want to be subscribed.

Issue Details

---

It's my understanding from https://www.unicode.org/reports/tr17 that the hyphen form is correct. So make strings and doc comments consistent.

Author:	danmoseley
Assignees:	danmoseley
Labels:	area-Meta
Milestone:	-

[tannergooding]

Looks like this just catches the all upper-case UTF8 to UTF-8. We still have a number of places that use other cases (such as utf8 or Utf8, same with 16) which presumably should also be fixed?
-- Notably lot more false positives due to locals with these names

[danmoseley]

Looks like this just catches the all upper-case UTF8 to UTF-8. We still have a number of places that use other cases (such as utf8 or Utf8, same with 16) which presumably should also be fixed?

I only looked in comments (doc comments only) and strings. Are there any there? Didn't see any. I could churn all the code but it didn't seem worth it as customers don't see it.

[danmoseley]

test failures are surely unrelated -- ios/tvos device not connecting, etc. seems to be a number of active failures in the repo right now.

[stephentoub]

These XML comments improvements won't automatically flow to the official docs. Do they need updating as well, or do they already do it the desired way?