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

support Unicode(or UTF-8 encoded) identifiers #830

Closed
Zhang-Junzhi opened this issue Jul 5, 2018 · 6 comments
Closed

support Unicode(or UTF-8 encoded) identifiers #830

Zhang-Junzhi opened this issue Jul 5, 2018 · 6 comments
Labels
future feature issues that may be handled in future versions i18n-tracker Group bringing to attention of Internationalization, or tracked by i18n but not needing response.

Comments

@Zhang-Junzhi
Copy link

Zhang-Junzhi commented Jul 5, 2018

I am wondering why wasm text format still doesn't support ientifiers outside of ASCII.

it's 2018, not 1998.

Why are English still the only allowed characters nowadays? ALL mordern languages support Unicode identifiers now. ALL.

So, please! Let's extend the allowed characters in identifiers to non-ASCII world.

@jfbastien
Copy link
Member

If we do so, we should follow https://unicode.org/reports/tr31/

@binji
Copy link
Member

binji commented Jul 8, 2018

The binary format already allows UTF-8 strings for the import and export names, as well as the debug name section names. The only limitation is in the text format identifiers, as you've said, and that's primarily because it was simpler to do so and the text format is not really intended to be written, except for in spec tests where the identifiers are included for clarity.

That said, I think the group would support a proposal to add Unicode identifiers. The process for changing the spec is here.

@steveklabnik
Copy link
Contributor

steveklabnik commented Jul 8, 2018 via email

@binji binji added the future feature issues that may be handled in future versions label May 22, 2019
@7ombie
Copy link

7ombie commented Apr 5, 2021

Is this still planned? I don't have much use for it personally, so am not worried about the timeframe, but am interested to know if anything concrete has been decided, either way.

@rossberg
Copy link
Member

rossberg commented Apr 6, 2021

Nobody has pushed for it by means of a concrete proposal, so no, currently there are no plans.

@7ombie
Copy link

7ombie commented Apr 6, 2021

Thank you, @rossberg. No worries.

@xfq xfq added the i18n-tracker Group bringing to attention of Internationalization, or tracked by i18n but not needing response. label Jun 27, 2022
@rossberg rossberg closed this as completed Aug 4, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
future feature issues that may be handled in future versions i18n-tracker Group bringing to attention of Internationalization, or tracked by i18n but not needing response.
Projects
None yet
Development

No branches or pull requests

7 participants