Re: Request: New KDE translation team for Brahui (brh) / براہوئی

Hello,

It seems that there is no glibc locale yet for brh. Without glibc locale,=20
there will be no locale to select the KDE software's language translation.=
=20
This has been discussed previously several times, see e.g. https://
mail.kde.org/pipermail/kde-i18n-doc/2025-February/002662.html for how to=20
proceed with glibc first.

Best,
Shinjo

2026=EB=85=84 2=EC=9B=94 28=EC=9D=BC =ED=86=A0=EC=9A=94=EC=9D=BC =EC=98=A4=
=ED=9B=84 9=EC=8B=9C 26=EB=B6=84 9=EC=B4=88 =EC=A4=91=EB=B6=80=EC=9C=A0=EB=
=9F=BD =ED=91=9C=EC=A4=80=EC=8B=9C=EC=97=90 Hammad =EB=8B=98=EC=9D=B4 =EC=
=93=B4 =EA=B8=80:
>  Hello KDE i18n team,
>=20
> I would like to start a KDE translation team for the Brahui language, as I
> could not find an existing Brahui team on KDE=E2=80=99s translation teams=
 list.
>=20
> Language details:
>=20
> English name: Brahui
> Native name (UTF-8): =D8=A8=D8=B1=D8=A7=DB=81=D9=88=D8=A6=DB=8C
> ISO 639-1: (none)
> ISO 639-2: (none)
> ISO 639-3: brh
> Primary script: Arabic-based script (RTL)
> Also used: Latin orthography known as =E2=80=9CBrolikva / Brahui Roman Li=
kvar=E2=80=9D (I
> propose starting with Arabic-script RTL.
> Regional usage: primarily Pakistan, also communities in Afghanistan, Iran,
> and the UAE
>=20
> Coordinator contact:
>=20
> Name: Hammad
> Email: [email protected]
>=20
> Please advise the correct next steps to create/enable the Brahui team and
> begin translation work (tools/workflow, where to submit translations, and
> any requirements for team setup).
>=20
> Thank you,
> Hammad
> [email protected]