Skip to content

Escaping: do we need Unicode escape sequences? #234

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
Closed
mihnita opened this issue May 11, 2022 · 4 comments
Closed

Escaping: do we need Unicode escape sequences? #234

mihnita opened this issue May 11, 2022 · 4 comments
Labels
resolve-candidate This issue appears to have been answered or resolved, and may be closed soon. syntax Issues related with syntax or ABNF

Comments

@mihnita
Copy link
Collaborator

mihnita commented May 11, 2022

No description provided.

@mihnita mihnita added the syntax Issues related with syntax or ABNF label May 11, 2022
@mihnita
Copy link
Collaborator Author

mihnita commented May 12, 2022

Comments migrated from the slides

\u1234

Slides comment, Addison Phillips (@aphillips), 6:44 AM Apr 21

This is Java/JS UTF-16 escaping. Should we also have a codepoint escaping scheme (\U10FFFF or \u{1234a})? FWIW, I don't mind this escaping.

Slides comment, Eemeli Aro (@eemeli), 7:52 AM Apr 21

Yes, probably. The list here is not meant to be exhaustive, but indicative.

@mihnita
Copy link
Collaborator Author

mihnita commented May 12, 2022

TLDR (my opinion): we should consider this syntax as "string in memory to be parsed by MessageFormat"
Unicode escapes belong in the storage layer.
Some storage formats already have ways their own escape rules, see issues #236

@eemeli eemeli added the resolve-candidate This issue appears to have been answered or resolved, and may be closed soon. label May 20, 2022
@eemeli
Copy link
Collaborator

eemeli commented May 20, 2022

Noting here that the current syntax proposal does not include Unicode escapes, and I am not aware of anyone currently advocating for adding them to the message-level syntax.

@romulocintra
Copy link
Collaborator

Consensus: No

@romulocintra romulocintra closed this as not planned Won't fix, can't repro, duplicate, stale May 23, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
resolve-candidate This issue appears to have been answered or resolved, and may be closed soon. syntax Issues related with syntax or ABNF
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@eemeli @mihnita @romulocintra