I think many former translators can agree that company-based translations have not proven to be effective over months after switching, moreover, the quality and slowness hurts the Discord localization part, your fans around the world.
The arguments you have provided to us while you were closing the program aren't really correct and it seems that you had some other motive to “escape” from community translations, maybe ever following the trends of other big companies to run away from the community.
Let us speak from our heart and nicely ask you to return to community-based translations and instead of avoiding us, work altogether, means show your support to the international community by listening to our feedback and providing small goods, such as asked profile badge. Because that will allow people that will be working for your good on globe market feel worthy and produce more qualitative results. This will also allow you to create another community of fans, like HypeSquad, but instead of going events they will be focusing on making Discord accessible for people all around a world, for people who don't know the English language.
- The NDA stuff, that was mentioned, that the company may translate things before they go public is actually not a point. Yes, secrets are okay, but when it comes to quality nobody cares about if translations were out when things released or soon after. Just update translation frequently or make it even near-live, as Telegram messenger did, but not sure if that possible with Crowdin.
This and the following bullet were edited per Manfre suggestions in comments that I personally agree with:
- There are other places where the translation community could not get into it because we weren't allowed to (e.g. Discord Support, Developer Documentation, Change Logs) these should be either translated by the community (proofreaders) or either we should have ways to report incorrect translations and possible improvements for the company's translation. Reports must have effective response too, not being “acknowledged” and stuck without any action for eternity.
• The developer documentation could be translated in the same GitHub repository where you are hosting your documentation: https://github.com/discordapp/discord-api-docs. The question is only the structure that is comfortable for both you and the community. Git should be known to developers, but improved CONTRIBUTING.md welcomed.
- When I said that you may listen to the community, there are few things, that we, as translators frequently asked for:
• Upload large strings (such as e-mails, pages) as separate text files, so we able to translate the sentence for sentence instead of the whole document. That is easy to proofread and translate. If you are not able to do it on Crowdin, use public GitHub repository instead and accept Pull Requests.
• Make and upload subtitles for video, so we able to make “Don't be a broom” videos accessible and maybe Ivan Popkov perestanet ispolzovat venik (excuse my Russian here)
• Use fonts that support all other languages, for example, Cyrillic is supported in Whitney font, but is not supported on any of the Discord sites, besides the client
• Provide context, make an official translators server, where people can ask a question and get answers. Most of the time we were searching for context on our own and rarely questions in the comments were read
• When it comes to change logs, allow a group of people selected by proofreaders, that will be checking change logs translation quality for their language or even translate on their own
- You have said that we can report things so they can get fixed, and as Russian proofreader that got more exclusive way to report all mistakes, I allowed our former community to report mistakes with me, but apparently, nobody cares about that being done this way.
Asking some users, they don't feel any effort by reporting mistakes. The same as they have given up over (really sorry) s--tty translations of articles on Support Site and Changelogs. Also, the question still remains: how are users supposed know where they can report absolutely gross translations, without knowing of heaven called “Discord translators” or having fellow DMP friend.
Previously they could go and apply on Crowdin by the link in settings and even that they did not get accepted most of the time in the team, because they did not read the project description that includes text they should pass in reason of applying, they were able to report mistake to proofreader, who nicely DM'ed them reason being denied to join the team.
So it would be awesome if you could not only return to community-based translations but allow basic users to report translation mistakes and localization team members to see and resolve them.
That could be a GitHub repository as I had, with the special form that calls GitHub API and creates an issue with the bot, so users don't need an additional account on a random site.
Or you could just make a Google Sheet and ask support team to fill out the reports there, so we as proofreaders can see it and report to our translators team members, or you could even make this doc public, as there no big reason to hide that, you surely don't want to include reporters e-mail or username, so that should be fine.
And this all about making translation process open and beneficial to you. When you pay probably much less, you get good quality translations and bring joy to people that volunteer for you, the same as Discord official server moderators.
Thank you for reading and I look forward for your answer on the issue, Discord.
If you are the one, who liked and still want to be included in open translation process of Discord, do not forget to vote up for this issue, so your voice counts. Have you anything to say or add, please comment on this idea.
Post ist für Kommentare geschlossen.