Skip to content

Translating Error Messages#293

Open
rdohms wants to merge 1 commit into
braincrafted:developfrom
rdohms:patch-5
Open

Translating Error Messages#293
rdohms wants to merge 1 commit into
braincrafted:developfrom
rdohms:patch-5

Conversation

@rdohms

@rdohms rdohms commented Aug 20, 2014

Copy link
Copy Markdown
Contributor

Without this call to trans the custom error messages are not translated, only the proper built-in ones.

Without this call to `trans` the custom error messages are not translated, only the proper built-in ones.
@mvrhov

mvrhov commented Aug 21, 2014

Copy link
Copy Markdown
Contributor

Hm.. Before your patch the code is same as in template provided by symfony. I guess that the problem lies somewhere else.?

@florianeckerstorfer

Copy link
Copy Markdown
Member

@mvrhov You're right.

We had the call to trans in there but I reverted the change in aa5795b. However, because I am not thinking about the feature I didn't add why I remove the call to trans.

I guess the problem is with the translation domains. When there is no translation domain given (like in this PR) custom error messages are not translated. On the other side when adding the translation domain the default error messages are not translated.

@althaus

althaus commented Oct 28, 2014

Copy link
Copy Markdown
Contributor

Shouldn't the translation domain default to messages somewhere?

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.

4 participants