Re: kde-i18n-doc Digest, Vol 276, Issue 1

El diumenge, 1 de mar=C3=A7 del 2026, a les 18:10:08 (Hora est=C3=A0ndard d=
=E2=80=99Europa=20
central), Hammad va escriure:
> Thank you for the clarification.
>=20
> Understood: KDE on Linux relies on glibc locales for language selection.
>=20
> I will work on creating a glibc locale first ( brh_PK.UTF-8),  and then
> submitting it upstream to glibc.
>=20
> Two quick questions so I follow the right path:
>=20
>    1.
>=20
>    Once a glibc locale exists (brh_PK.UTF-8), is that sufficient for KDE =
to
>    add/enable the Brahui translation team, or or are there other
> prerequisites before you can proceed?

That should probably be enough.

>    2.
>=20
>    Do you recommend starting with one locale only (brh_PK) first, and
>    considering additional region variants later (e.g., Afghanistan/Iran)
> only if needed?

That's a question you should ask the glibc/locale developers, they will be=
=20
able to answer you better than us.

Cheers,
  Albert

>=20
> Thanks again,
> Hammad
>=20
> On Sun, 1 Mar 2026 at 17:00, <[email protected]> wrote:
> > Send kde-i18n-doc mailing list submissions to
> >=20
> >         [email protected]
> >=20
> > To subscribe or unsubscribe via the World Wide Web, visit
> >=20
> >         https://mail.kde.org/mailman/listinfo/kde-i18n-doc
> >=20
> > or, via email, send a message with subject or body 'help' to
> >=20
> >         [email protected]
> >=20
> > You can reach the person managing the list at
> >=20
> >         [email protected]
> >=20
> > When replying, please edit your Subject line so it is more specific
> > than "Re: Contents of kde-i18n-doc digest..."
> >=20
> > Today's Topics:
> >    1. Request: New KDE translation team for Brahui (brh) /
> >   =20
> >       =D8=A8=D8=B1=D8=A7=DB=81=D9=88=D8=A6=DB=8C (Hammad)
> >   =20
> >    2. Re: Request: New KDE translation team for Brahui (brh) /
> >   =20
> >       =D8=A8=D8=B1=D8=A7=DB=81=D9=88=D8=A6=DB=8C (Shinjo Park)
> >=20
> > ----------------------------------------------------------------------
> >=20
> > Message: 1
> > Date: Sun, 1 Mar 2026 01:26:09 +0500
> > From: Hammad <[email protected]>
> > To: [email protected]
> > Subject: Request: New KDE translation team for Brahui (brh) /
> >=20
> >         =D8=A8=D8=B1=D8=A7=DB=81=D9=88=D8=A6=DB=8C
> >=20
> > Message-ID:
> >         <CALoFT+6KQb3PnJ_AS02=3DOJhV8J5AcP=3D
> >=20
> > [email protected]>
> > Content-Type: text/plain; charset=3D"utf-8"
> >=20
> >  Hello KDE i18n team,
> >=20
> > I would like to start a KDE translation team for the Brahui language, a=
s I
> > could not find an existing Brahui team on KDE=E2=80=99s translation tea=
ms 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 =
Likvar=E2=80=9D (I
> > propose starting with Arabic-script RTL.
> > Regional usage: primarily Pakistan, also communities in Afghanistan, Ir=
an,
> > 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 a=
nd
> > begin translation work (tools/workflow, where to submit translations, a=
nd
> > any requirements for team setup).
> >=20
> > Thank you,
> > Hammad
> > [email protected]
> > -------------- next part --------------
> > An HTML attachment was scrubbed...
> > URL: <
> > http://mail.kde.org/pipermail/kde-i18n-doc/attachments/20260301/fc3ac5d=
b/a
> > ttachment-0001.htm
> >=20
> >=20
> > ------------------------------
> >=20
> > Message: 2
> > Date: Sat, 28 Feb 2026 22:01:23 +0100
> > From: Shinjo Park <[email protected]>
> > To: [email protected]
> > Subject: Re: Request: New KDE translation team for Brahui (brh) /
> >=20
> >         =D8=A8=D8=B1=D8=A7=DB=81=D9=88=D8=A6=DB=8C
> >=20
> > Message-ID: <5972745.DvuYhMxLoT@ainazi>
> > Content-Type: text/plain; charset=3D"utf-8"
> >=20
> > Hello,
> >=20
> > It seems that there is no glibc locale yet for brh. Without glibc local=
e,
> > there will be no locale to select the KDE software's language translati=
on.
> > 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
> > proceed with glibc first.
> >=20
> > Best,
> > Shinjo
> >=20
> > 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
> >=20
> > I
> >=20
> > > could not find an existing Brahui team on KDE=E2=80=99s translation t=
eams 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 Roma=
n Likvar=E2=80=9D
> > > (I
> > > propose starting with Arabic-script RTL.
> > > Regional usage: primarily Pakistan, also communities in Afghanistan,
> >=20
> > Iran,
> >=20
> > > 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]
> >=20
> > ------------------------------
> >=20
> > Subject: Digest Footer
> >=20
> > _______________________________________________
> > kde-i18n-doc mailing list
> > [email protected]
> > https://mail.kde.org/mailman/listinfo/kde-i18n-doc
> >=20
> >=20
> > ------------------------------
> >=20
> > End of kde-i18n-doc Digest, Vol 276, Issue 1
> > ********************************************