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
Next available day/hour is not properly translated #9285
Comments
@micheh Thank you for reporting this. If possible, could you share a screenshot of it? Which language are you using? The only hard-coded string in this method would be |
Hello @vishnu-narayanan, here is a screenshot: I tested it with German (de), but could replicate the issue in other languages like French (fr), Italian (it) and Spanish (es). Almost all methods in
chatwoot/app/javascript/widget/mixins/nextAvailabilityTime.js Lines 161 to 165 in 8957277
Line 172 returns the hard coded string
chatwoot/app/javascript/widget/mixins/nextAvailabilityTime.js Lines 146 to 154 in 8957277
In the German language, the relative time should be in another place. |
@micheh Thank you for reporting the issue. We are currently working on a solution to fix the translation problem, as there is an open PR to address it. #9097 |
Describe the bug
When the working hours are set, the widget shows the time or day when agents will be back online. This works fine in English, but not so much in other languages. The problem is that there are some hard coded English strings in the mixing timeLeftToBackInOnline or the translations are not available like
tomorrow
:chatwoot/app/javascript/widget/mixins/nextAvailabilityTime.js
Lines 156 to 176 in 8957277
This results in a mix of English and the other locale. In addition, the date string is added after the translation
REPLY_TIME.BACK_IN
. Other languages may have a different sentence structure and even if the relative dates strings are translated correctly, it will look strange when the time is added at the end.To Reproduce
Expected behavior
No response
Environment
app.chatwoot.com
Cloud Provider
None
Platform
None
Operating system
No response
Browser and version
No response
Docker (if applicable)
No response
Additional context
No response
The text was updated successfully, but these errors were encountered: