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

Internationalization of built in messages #3

Open
psychoslave opened this issue Nov 19, 2016 · 0 comments
Open

Internationalization of built in messages #3

psychoslave opened this issue Nov 19, 2016 · 0 comments

Comments

@psychoslave
Copy link
Owner

Messages like "lexical element too long" should be localizable.

This could be made independent from the localization of built in tokens. That is, a built in message referring to "" might let the token untranslated if the platform doesn't use translated tokens.

Indeed, the platform should take into account environment variable, like LANG, to determine the language in which messages should appear. But this should probably not be used regarding autoload of localized version of tokens. For this, it would probably more relevant to rely on explicit statements which load the localized tokens and other possible localized syntactic sugar. Thus said, if localized built in tokens went loaded, then the messages should also reflect this change.

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

No branches or pull requests

1 participant