Re: Creating Belarusian Team (be)
Luigi Toscano <[email protected]> Sun, 22 Feb 2026 21:20:46 +0100
| Newsgroups | gmane.comp.kde.devel.internationalization-and-documentation |
|---|---|
| Message-ID | <[email protected]> |
Гулкі Смоўж ha scritto: > Hi everyone! > > It seems that there is no active Belarusian team > <https://l10n.kde.org/team-infos.php?teamcode=be> at the moment and I would > like to create it. > I am experienced translator into Belarusian and know other translators, that > would like to organize ourselves and translate KDE into our language. > Also, it seems like the Chinese team has a Crowdin project with automated > integration through GitHub. If we could cooperate to make translations at > Crowdin, it would be great. Please do not use crowdin. The team using it is what I would call an historical accident, but starting its usage for a new team is not solution. Crowdin is really bad: it doesn't provide the credit for the translators involved. What I've seen with crowdin (and other "open" web tools) is that people just fix the string they need without caring for the existing strings, leading to ugly inconsistent translations. My suggestion is to split the files between people, by logical groups (similar items together), and review each other works. But really, no Crowdin. That said, there have been instructions on how to start or restart a team, for example here: https://mail.kde.org/pipermail/kde-i18n-doc/2025-September/002973.html https://mail.kde.org/pipermail/kde-i18n-doc/2025-September/002983.html But please note that for Belarusian there is at least one translator active, who is focused on Gcompris. but at least he knows the workflow and you definitely need to coordinate with him. There was also another translator active until one year ago, who may help. I've added both in CC. Ciao -- Luigi