Hi! We’re evaluating whether it makes sense to continue translating all of our Mattermost server-side components, such as logs, database error messages, API errors, and email templates, into all of our supported languages. And we need your input!
Translating server-side components is a great idea, in theory. All text in a product should be presented to a user in the user’s local language. It’s a best practice approach for companies with global reach. From a user’s perspective, trying to troubleshoot an error message in a language you don’t understand is irritating to say the least!
However, we’re translating some server-side strings that aren’t visible to end users, and we’re wondering whether that’s the best use of a translator’s time and effort. The technical nature of logs and database error messages, which are designed for and consumed by developers and debugger tools, makes those strings challenging to translate into languages beyond English.
If we stopped providing translations for server-side components that aren’t visible to end users, these components would display in English. System Admins will likely find more relevant troubleshooting information or workarounds by searching for the string online in English, rather than searching the translated string. System Admins would also continue to share such data with Mattermost Support in English, as the vast majority of our customers do today. (It’s rare that we receive translated logs or errors in the context of a customer support ticket.)
We want your input on this important decision! As a Mattermost community member, product user, system admin, customer, advocate, developer, integrator, or tool evaluator – if Mattermost stopped translating server-side components that aren’t visible to users, what impact would this have for you? Would this impact you negatively, and if so, how?
Share your thoughts with us here in this forum thread, or join us in the i18n - Localization Community channel to say hello and tell us what you think.