Support multiple translations with different message domains #148
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
Any chance a release with this is forthcoming? I think getting back to a single maintained package would be great. I am trying to get Flask-Security back in a maintained state - and it would be great to have a dependency that is maintained. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This pull request is to add a feature that support multiple language catalogs with different localization domains which is provided by flask-babelex.
Currently many flask extensions use flask-babelex to package their own localization file(s), e.g. flask-security, flask-admin etc. There are super annoying incompatibilities(mattupstate/flask-security#715, lingthio/Flask-User#195) when combined flask-babelex with flask-babel and the development of flask-babelex seems stuck.