Subtitle Edit currently relies on JSON files for localization, some of which contain AI-generated translations of quite dubious quality; at least in the languages I understand. Some strings are directly incomprehensible.. While using JSON files makes localisation accessible, it makes it very difficult for those of us who want to contribute high-quality, manual corrections. Managing translation pull requests manually also introduces formatting issues, merge conflicts, and overhead for maintainers. Also JSON scales really poorly with a high number of strings. SE has over 3.000!
I propose integrating hosted Weblate into the Subtitle Edit repository workflow, which is free since Subtitle Edit is a libre/open-source project. This allows the use of translation memory, project dictionaries, QA tools, fuzzy flagging and all the tools that make us translators happy.
I contribute translation and linguistic QA to several other open source projects across different l10n-platforms and Weblate provides one of the smoothest workflow for translators in my opinion. The workflow for maintainers can be fully automated. Weblate supports json, so there should be no need to touch the actual codebase. Only the translation source needs to be updated.
I hope you'll consider my proposal. I usually avoid contributing to projects that rely on raw json for localisation because it is so daunting, but I use and enjoy Subtitle Edit so often, that I really want it to have high quality UI experience.
Til slut vil jeg bare gerne takke dig for et virkeligt godt stykke software. Jeg har brugt SE i årevis. Jeg bruger både windows og linux, så jeg er virkeligt glad for at 5'eren nu kan køre direkte på linux. Det er en kæmpe forbedring i forhold til at køre det gennem mono. Glæder mig til at se SE på Flathub
Eksempel på frygtelig maskinoversættelse af »Dual speakers«, som skulle have være »To talere« eller »Dialog«
Subtitle Edit currently relies on JSON files for localization, some of which contain AI-generated translations of quite dubious quality; at least in the languages I understand. Some strings are directly incomprehensible.. While using JSON files makes localisation accessible, it makes it very difficult for those of us who want to contribute high-quality, manual corrections. Managing translation pull requests manually also introduces formatting issues, merge conflicts, and overhead for maintainers. Also JSON scales really poorly with a high number of strings. SE has over 3.000!
I propose integrating hosted Weblate into the Subtitle Edit repository workflow, which is free since Subtitle Edit is a libre/open-source project. This allows the use of translation memory, project dictionaries, QA tools, fuzzy flagging and all the tools that make us translators happy.
I contribute translation and linguistic QA to several other open source projects across different l10n-platforms and Weblate provides one of the smoothest workflow for translators in my opinion. The workflow for maintainers can be fully automated. Weblate supports json, so there should be no need to touch the actual codebase. Only the translation source needs to be updated.
I hope you'll consider my proposal. I usually avoid contributing to projects that rely on raw json for localisation because it is so daunting, but I use and enjoy Subtitle Edit so often, that I really want it to have high quality UI experience.
Til slut vil jeg bare gerne takke dig for et virkeligt godt stykke software. Jeg har brugt SE i årevis. Jeg bruger både windows og linux, så jeg er virkeligt glad for at 5'eren nu kan køre direkte på linux. Det er en kæmpe forbedring i forhold til at køre det gennem mono. Glæder mig til at se SE på Flathub
Eksempel på frygtelig maskinoversættelse af »Dual speakers«, som skulle have være »To talere« eller »Dialog«
