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 (I18N) #143

Open
domi41 opened this issue Apr 30, 2020 · 2 comments
Open

Internationalization (I18N) #143

domi41 opened this issue Apr 30, 2020 · 2 comments

Comments

@domi41
Copy link

domi41 commented Apr 30, 2020

Hello !

Any plans for I18N of hamcrest ?

      Assertion Failed: 
      Expected: <32>
           but: was <2>

I see that some of the tests rely on parsing the error message in english.

Are there any pitfalls or caveats I should be aware of?
Suggestions of L10N implementation? (like the format of the language files)

Rationale for I18N

Behavior-Driven with Gherkin feature files, using hamcrest for assertions in steps.
The output of the runner will be read by everyone, including the informatically illiterate and monoglot.

@brunns
Copy link
Member

brunns commented Apr 30, 2020

Interesting idea - but I'm not sure we would have the community support to provide and maintain the translations. If anyone has any ideas, I'm all ears.

@domi41
Copy link
Author

domi41 commented Apr 30, 2020

The Assertion Failed message comes from the AssertionError itself, right?
I can't find useful information on how to I18N python's built-in exceptions.

Should we use our own, extended AssertionError ? Is there another way ?

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

2 participants