ICU-22851 A named-element is an element, not a set

[eggrobin]

Also include it in string-element: https://www.unicode.org/reports/tr61/#string-element.

Checklist

• Required: Issue filed: ICU-22851
• Required: The PR title must be prefixed with a JIRA Issue number. Example: "ICU-NNNNN Fix xyz"
• Required: Each commit message must be prefixed with a JIRA Issue number. Example: "ICU-NNNNN Fix xyz"
• Issue accepted (done by Technical Committee after discussion)
• Tests included, if applicable
• API docs and/or User Guide docs changed or added, if applicable
• Approver: Feel free to merge on my behalf

[markusicu]

remove "named-element" from the preceding comment

[markusicu]

Do you mean

Suggested change

	// {\N{LATIN CAPITAL LETTER Z} was a well-formed string literal, but then the second }
	// {\N{LATIN CAPITAL LETTER Z}} was a well-formed string literal, but then the second }

?

[eggrobin]

I do not. {\N{LATIN CAPITAL LETTER Z} was a well-formed string literal whose value was N{LATINCAPITALLETTERZ.

[markusicu]

Ok, but there is no “second }” to be unpaired, so I don't understand the second part of the sentence.

[eggrobin]

There is a second } in {\N{LATIN CAPITAL LETTER Z}eichenkette}.

[markusicu]

I get it now -- there is no second } in the comment, but there is in the test case... nvm

[jira-pull-request-webhook]

Hooray! The files in the branch are the same across the force-push. 😃

~ Your Friendly Jira-GitHub PR Checker Bot