-
Notifications
You must be signed in to change notification settings - Fork 65
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
How translate error messages? #125
Comments
You would have to translate that message yourself and add to your translation file(s). Then call |
@kbond is exactly correct! In your controller (I'm assuming you used MakerBundle to generate your setup), in a try/catch you are passed a This is probably something we should add to the docs. |
There are PRs open in the Symfony Demo repository that demonstrate how this is done. I'm hoping to get some time to head over there and put the finishing touches on those PR's soon. |
Hi there, would it be useful to add these strings to the translation files of the bundle? |
@codedmonkey, is this what you mean? |
Hey guys! I suggested translating error messages in #206 that was already merged 🎉 - but we still need to merge related PR in Maker, see symfony/maker-bundle#1059 . Please, give it a try and review if you want! Also, feel free to help translating error messages to other languages, currently it's translated into en, ru and uk: reset-password-bundle/src/Resources/translations/ResetPasswordBundle.en.xlf Lines 25 to 48 in d7f9fda
Btw, for now you can easily translate those messages yourself if needed, find a workaround here: #202 (comment) |
I'm closing this - symfony/maker-bundle#1059 is merged and Maker v1.37.0 is released. Now this bundle only needs missing translations. If you already generated reset password code with Maker before - please, update it according to the new changes in Maker, see symfony/maker-bundle#1059 for the help |
I have this message:
How can I translate that please?
This error message is not inside a translation file.
Thanks.
The text was updated successfully, but these errors were encountered: