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

Delete messy example #277

Merged
merged 1 commit into from
Nov 3, 2022
Merged

Delete messy example #277

merged 1 commit into from
Nov 3, 2022

Conversation

glyn
Copy link
Collaborator

@glyn glyn commented Oct 19, 2022

Fixes #274

@gregsdennis
Copy link
Collaborator

Do we intend to replace this with anything? What is its purpose in being here?

@timbray
Copy link
Contributor

timbray commented Nov 3, 2022

The N-1 line also illustrates the point so I think it's probably OK to leave it?

@glyn glyn merged commit c4ab972 into main Nov 3, 2022
@glyn glyn deleted the 274-delete-messy-example branch November 3, 2022 09:21
@cabo
Copy link
Member

cabo commented Nov 3, 2022

Sorry, I didn't pay attention.
The purpose of this example was to show that escaped characters are normalized into their actual equivalents (unless there is a reason not to do so).

The messiness is a workaround for xml2rfc bugs. I'm confident we can get these bugs fixed before this is published; otherwise we might indeed want to skip this example.

@glyn
Copy link
Collaborator Author

glyn commented Nov 3, 2022

Why doesn't the $["\u0061"] example already show that an escaped character is normalised into its actual equivalent ("a")?

@cabo
Copy link
Member

cabo commented Nov 3, 2022

It does. Many implementers will however think that this only applies to 95-ASCII characters (there is no reason for thinking that, but it is a highly likely misunderstanding).

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

Successfully merging this pull request may close these issues.

Table 15
4 participants