You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
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.The text was updated successfully, but these errors were encountered: