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

Localization support #37

Open
wants to merge 8 commits into
base: dev
Choose a base branch
from
Open

Localization support #37

wants to merge 8 commits into from

Conversation

NebelNidas
Copy link
Collaborator

@NebelNidas NebelNidas commented Jun 17, 2023

Inspired by Enigma's and JADX's equivalents, but heavily stripped down. Only supports mapping format names for now, exception messages are going to be tackled in a separate PR.

Copy link
Member

@modmuss50 modmuss50 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I dont think we should localise error messages like this
It makes it harder to search for solutions, harder for people trying to provide support, and doesn't really benefit users. We dont localise error messages in other projects, especially none user facing ones like this.

@NebelNidas NebelNidas marked this pull request as ready for review October 16, 2023 11:42
@NebelNidas NebelNidas marked this pull request as draft March 28, 2024 19:34
@sfPlayer1
Copy link
Contributor

We could maybe introduce error codes that make it accessible for replacement on the embedding application side?

@NebelNidas
Copy link
Collaborator Author

NebelNidas commented Apr 19, 2024

That's the goal, having a central ErrorMessages class holding all the error messages MIO uses in the form of Translatables. Consumers can either translate the Translatable to a given locale, or manually check for equality with a given error message.

But as mentioned above, that's going to be a separate PR (probably after #94 is merged)

@NebelNidas NebelNidas marked this pull request as ready for review April 19, 2024 16:35
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

Successfully merging this pull request may close these issues.

3 participants