This object is in archive!
"response" is a strange term
I find "response" to be a weird term for what other call bugs, issues, tickets, etc. When a user creates a new entry, he's not "responding" to anything. Comments to that entry are responses to it, but not the entry itself that started the thread.
Now, I understand that, for branding purposes, "response" will probably have to be kept as default (I encourage you to rethink that decision nevertheless), but there should be an easy and well-advertised way to use a different term site-wide.
In 3.1 release, we have Feedback module and renamed all responses to be Topics which are:
In 3.1 release, we have Feedback module and renamed all responses to be Topics which are:
If you don't like anything in words or expressions, you can translate anything or rename any wording in administration area, using translation tool.
Also, use email templates to edit any notification email.
Check in Admin Manual, Translation & Languages article
If you don't like anything in words or expressions, you can translate anything or rename any wording in administration area, using translation tool.
Also, use email templates to edit any notification email.
Check in Admin Manual, Translation & Languages article
Thanks for the fast response. However, what I'm talking about is not about personal preferences: there are definitely some odd grammar constructs in the platform (which are understandable if the developers of the platform aren't native English speakers).
Tweaking a specific installation won't solve the larger problem that other admins (and most importantly, other users) will be exposed to these slightly strange strings. It ends up having an effect on the perception of the quality of the product.
I'd love to be able to help with suggesting tweaks to UseResponse's interface strings, and I'm sure others would chime in too if a way to do so was available. I often contribute translations to projects in sites such as launchpad.net or translatewiki.net and it works very well.
If you adhered to such a platform (or provided something similar built in-house) this would allow not only suggestions for small English fixes, but also crowdsourced translation of the whole platform into many languages :)
Thanks for the fast response. However, what I'm talking about is not about personal preferences: there are definitely some odd grammar constructs in the platform (which are understandable if the developers of the platform aren't native English speakers).
Tweaking a specific installation won't solve the larger problem that other admins (and most importantly, other users) will be exposed to these slightly strange strings. It ends up having an effect on the perception of the quality of the product.
I'd love to be able to help with suggesting tweaks to UseResponse's interface strings, and I'm sure others would chime in too if a way to do so was available. I often contribute translations to projects in sites such as launchpad.net or translatewiki.net and it works very well.
If you adhered to such a platform (or provided something similar built in-house) this would allow not only suggestions for small English fixes, but also crowdsourced translation of the whole platform into many languages :)
Waldir,
We are open to suggestions and the best way here will be downloading free package and we'll provide you translations from latest release of corporate package and you can fix some wordings and provide us with the result.
We'll check on fixes and implement what we think is worth of fixing and let you know.
Let me know if you are open for this and I'll send you archive with latest translation files.
Waldir,
We are open to suggestions and the best way here will be downloading free package and we'll provide you translations from latest release of corporate package and you can fix some wordings and provide us with the result.
We'll check on fixes and implement what we think is worth of fixing and let you know.
Let me know if you are open for this and I'll send you archive with latest translation files.
I understand that setting up a whole translation infrastructure may be beyond your current plans. That would be the ideal solution, as the workload would be distributed across the interested users.
Meanwhile, yes, I can try to help the way you mention, but of course, I can't promise doing it very fast if the file is very long :)
I understand that setting up a whole translation infrastructure may be beyond your current plans. That would be the ideal solution, as the workload would be distributed across the interested users.
Meanwhile, yes, I can try to help the way you mention, but of course, I can't promise doing it very fast if the file is very long :)
In 3.1 release, we have Feedback module and renamed all responses to be Topics which are:
In 3.1 release, we have Feedback module and renamed all responses to be Topics which are:
Replies have been locked on this page!