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

Unicode support #280

Closed
gunnarx opened this issue May 3, 2021 · 2 comments · Fixed by #716
Closed

Unicode support #280

gunnarx opened this issue May 3, 2021 · 2 comments · Fixed by #716

Comments

@gunnarx
Copy link
Contributor

gunnarx commented May 3, 2021

Placeholder for discussion on allowable characters in the YAML definitions.

  • Today: Which are the allowable characters, for example in signal names (right now only letters, numbers and "." encoded in ASCII seems assumed)?
  • Future: What are future rules taking into account non-english languages, as well as the general consensus in many programming environments to use unicode file formats (UTF8 would be a good small step of course).
  • Also, make sure to compare to YAML specs so that the result is still YAML compliant.
@crea7or
Copy link
Contributor

crea7or commented Sep 11, 2021

Since JSON and YAML are UTF-8 by default there are not so many choices.

@oliveirarleo
Copy link
Contributor

Well, I think more support is good, but this may interfere with some things already defined, for example . and # are already reserve.

Another thing is that someone will be able to use emojis and other characters that may not be desirable.

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

Successfully merging a pull request may close this issue.

4 participants