Bug 502009

Summary:	No response from KDE Sinhala translation maintainers
Product:	[Translations] i18n	Reporter:	malaka tharumuthu <malakat100>
Component:	general	Assignee:	Albert Astals Cid <aacid>
Status:	RESOLVED FIXED
Severity:	normal	CC:	jlp
Priority:	NOR
Version First Reported In:	unspecified
Target Milestone:	---
Platform:	Other
OS:	Linux
Latest Commit:		Version Fixed In:
Sentry Crash Report:

Description malaka tharumuthu 2025-03-26 07:13:08 UTC

Hello,  

I am interested in contributing to KDE by translating it into Sinhala. However, I have been unable to reach the Sinhala translation team via email and the KDE localization page (https://l10n.kde.org/teams/si/) seems to be inaccessible. Additionally, I tried joining the KDE Matrix server, but registration is disabled.  

Could you please guide me on how to get involved with KDE Sinhala translations? If the team is inactive, can I help revive or take responsibility for the translations?  

Thank you for your time and assistance.  

Best regards,  
Malaka Tharumuthu

Comment 1 Jure Repinc 2025-03-26 11:29:18 UTC

ISO code "sl" is for Slovenian language, Sinhala should be "si". Since the component for "si" is missing I set it to "general".

Comment 2 Jure Repinc 2025-03-26 11:37:01 UTC

BTW the webpage for Sinhala localisation team (https://l10n.kde.org/team-infos.php?teamcode=si) also lists a mailing list you can use to try to reach previous contributors: https://mail.kde.org/mailman/listinfo/kde-l10n-si

Comment 3 malaka tharumuthu 2025-03-26 12:56:24 UTC

Hi Jure,

Thank you for the clarification regarding the language code and for providing the updated links to the Sinhala localization team.

I had already attempted to reach out via the mailing list for few months now , but my request hasn't been approved, and I haven't received any response.

Comment 4 Albert Astals Cid 2025-03-26 16:08:21 UTC

Thanks for wanting to translate to Sinhala.

Please subscribe to https://mail.kde.org/mailman/listinfo/kde-i18n-doc and send a message there with a copy&paste of what you wrote here.

Sorry for making jump thorugh more hoops, but the mailing list is where we usually handle these kind of things.