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

Hammad hammadalo99 at gmail.com
Sun Mar 1 17:10:08 GMT 2026


Thank you for the clarification.

Understood: KDE on Linux relies on glibc locales for language selection.

I will work on creating a glibc locale first ( brh_PK.UTF-8),  and then
submitting it upstream to glibc.

Two quick questions so I follow the right path:

   1.

   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?
   2.

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

Thanks again,
Hammad



On Sun, 1 Mar 2026 at 17:00, <kde-i18n-doc-request at kde.org> wrote:

> Send kde-i18n-doc mailing list submissions to
>         kde-i18n-doc at kde.org
>
> To subscribe or unsubscribe via the World Wide Web, visit
>         https://mail.kde.org/mailman/listinfo/kde-i18n-doc
> or, via email, send a message with subject or body 'help' to
>         kde-i18n-doc-request at kde.org
>
> You can reach the person managing the list at
>         kde-i18n-doc-owner at kde.org
>
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of kde-i18n-doc digest..."
>
>
> Today's Topics:
>
>    1. Request: New KDE translation team for Brahui (brh) /
>       براہوئی (Hammad)
>    2. Re: Request: New KDE translation team for Brahui (brh) /
>       براہوئی (Shinjo Park)
>
>
> ----------------------------------------------------------------------
>
> Message: 1
> Date: Sun, 1 Mar 2026 01:26:09 +0500
> From: Hammad <hammadalo99 at gmail.com>
> To: kde-i18n-doc at kde.org
> Subject: Request: New KDE translation team for Brahui (brh) /
>         براہوئی
> Message-ID:
>         <CALoFT+6KQb3PnJ_AS02=OJhV8J5AcP=
> KkuB9zK9oFw0zgLPhgA at mail.gmail.com>
> Content-Type: text/plain; charset="utf-8"
>
>  Hello KDE i18n team,
>
> I would like to start a KDE translation team for the Brahui language, as I
> could not find an existing Brahui team on KDE’s translation teams list.
>
> Language details:
>
> English name: Brahui
> Native name (UTF-8): براہوئی
> ISO 639-1: (none)
> ISO 639-2: (none)
> ISO 639-3: brh
> Primary script: Arabic-based script (RTL)
> Also used: Latin orthography known as “Brolikva / Brahui Roman Likvar” (I
> propose starting with Arabic-script RTL.
> Regional usage: primarily Pakistan, also communities in Afghanistan, Iran,
> and the UAE
>
> Coordinator contact:
>
> Name: Hammad
> Email: hammadalo99 at gmail.com
>
> 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).
>
> Thank you,
> Hammad
> hammadalo99 at gmail.com
> -------------- next part --------------
> An HTML attachment was scrubbed...
> URL: <
> http://mail.kde.org/pipermail/kde-i18n-doc/attachments/20260301/fc3ac5db/attachment-0001.htm
> >
>
> ------------------------------
>
> Message: 2
> Date: Sat, 28 Feb 2026 22:01:23 +0100
> From: Shinjo Park <kde at peremen.name>
> To: kde-i18n-doc at kde.org
> Subject: Re: Request: New KDE translation team for Brahui (brh) /
>         براہوئی
> Message-ID: <5972745.DvuYhMxLoT at ainazi>
> Content-Type: text/plain; charset="utf-8"
>
> Hello,
>
> It seems that there is no glibc locale yet for brh. Without glibc locale,
> there will be no locale to select the KDE software's language translation.
> 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.
>
> Best,
> Shinjo
>
> 2026년 2월 28일 토요일 오후 9시 26분 9초 중부유럽 표준시에 Hammad 님이 쓴 글:
> >  Hello KDE i18n team,
> >
> > I would like to start a KDE translation team for the Brahui language, as
> I
> > could not find an existing Brahui team on KDE’s translation teams list.
> >
> > Language details:
> >
> > English name: Brahui
> > Native name (UTF-8): براہوئی
> > ISO 639-1: (none)
> > ISO 639-2: (none)
> > ISO 639-3: brh
> > Primary script: Arabic-based script (RTL)
> > Also used: Latin orthography known as “Brolikva / Brahui Roman Likvar” (I
> > propose starting with Arabic-script RTL.
> > Regional usage: primarily Pakistan, also communities in Afghanistan,
> Iran,
> > and the UAE
> >
> > Coordinator contact:
> >
> > Name: Hammad
> > Email: hammadalo99 at gmail.com
> >
> > 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).
> >
> > Thank you,
> > Hammad
> > hammadalo99 at gmail.com
>
>
>
>
>
>
> ------------------------------
>
> Subject: Digest Footer
>
> _______________________________________________
> kde-i18n-doc mailing list
> kde-i18n-doc at kde.org
> https://mail.kde.org/mailman/listinfo/kde-i18n-doc
>
>
> ------------------------------
>
> End of kde-i18n-doc Digest, Vol 276, Issue 1
> ********************************************
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.kde.org/pipermail/kde-i18n-doc/attachments/20260301/198a4b13/attachment.htm>


More information about the kde-i18n-doc mailing list