https://bugs.kde.org/show_bug.cgi?id=423171
--- Comment #3 from Claudius Ellsel <claudius.ell...@live.de> --- Ideally, there would be one unified solution and workflow that is so nice that all teams use it. I guess that having as less manual steps involved as possible for maintainance like manual merging will be beneficial. I am not experienced on how to manage localization, but I'd propose something like the following: - Manage translation files in a repository on GitLab (thus one could use the web editor to quickly create a merge request for changes). Maybe it can also be integrated into each project's git repository there (I am not sure whether this is a common practice and would be sensible for KDE). - Use a web based translation tool for all languages as the standard way of translating to make contributions easier (lower the barrier and offer nice UX). That could be hosted at https://l10n.kde.org/ and replace the current site there. - Ideally maintain a workflow for translators that prefer to use an offline workflow (don't know whether there are currently offline translation tools in use). -- You are receiving this mail because: You are watching all bug changes.
