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

Allow non-ASCII identifiers #117

Open
stasm opened this issue May 21, 2018 · 3 comments
Open

Allow non-ASCII identifiers #117

stasm opened this issue May 21, 2018 · 3 comments
Labels
forwards incompatible Old parsers won't parse newer files. FUTURE Ideas and requests to consider after Fluent 1.0 needs: Unicode feedback syntax

Comments

@stasm
Copy link
Contributor

stasm commented May 21, 2018

This popped up in #90. Relaxing the grammar of identifiers is a harder task but it may be worth doing in Fluent primarily for attributes of terms, and in the future—for private terms (i.e. terms which are not checked for presence against the source language). The asymmetry of Fluent makes it a natural choice to spell out these identifiers using the native language.

There's UAX31 which should be a good start and base for the research here.

@stasm stasm added forwards incompatible Old parsers won't parse newer files. needs: Unicode feedback FUTURE Ideas and requests to consider after Fluent 1.0 labels May 22, 2018
@zbraniecki
Copy link
Collaborator

References:

Seems like there's a good precedence.

@zbraniecki
Copy link
Collaborator

@stasm
Copy link
Contributor Author

stasm commented Aug 9, 2018

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
forwards incompatible Old parsers won't parse newer files. FUTURE Ideas and requests to consider after Fluent 1.0 needs: Unicode feedback syntax
Projects
None yet
Development

No branches or pull requests

2 participants