Re: kde-i18n-doc Digest, Vol 276, Issue 1
Hammad <[email protected]> Sun, 1 Mar 2026 22:10:08 +0500
| Newsgroups | gmane.comp.kde.devel.internationalization-and-documentation |
|---|---|
| Message-ID | <CALoFT+6gCJdTmZhS+o34+c5wyT0tia5OfSSRxpmcvxvD3-mqiQ@mail.gmail.com> |
--0000000000007f0a56064bf98b07 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable 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 prerequisi= tes 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) on= ly if needed? Thanks again, Hammad On Sun, 1 Mar 2026 at 17:00, <[email protected]> wrote: > Send kde-i18n-doc mailing list submissions to > [email protected] > > 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 > [email protected] > > You can reach the person managing the list at > [email protected] > > 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) / > =D8=A8=D8=B1=D8=A7=DB=81=D9=88=D8=A6=DB=8C (Hammad) > 2. Re: Request: New KDE translation team for Brahui (brh) / > =D8=A8=D8=B1=D8=A7=DB=81=D9=88=D8=A6=DB=8C (Shinjo Park) > > > ---------------------------------------------------------------------- > > 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) / > =D8=A8=D8=B1=D8=A7=DB=81=D9=88=D8=A6=DB=8C > Message-ID: > <CALoFT+6KQb3PnJ_AS02=3DOJhV8J5AcP=3D > [email protected]> > Content-Type: text/plain; charset=3D"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=E2=80=99s translation teams= list. > > Language details: > > 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 > > Coordinator contact: > > Name: Hammad > Email: [email protected] > > 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 > [email protected] > -------------- 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 <[email protected]> > To: [email protected] > Subject: Re: Request: New KDE translation team for Brahui (brh) / > =D8=A8=D8=B1=D8=A7=DB=81=D9=88=D8=A6=DB=8C > Message-ID: <5972745.DvuYhMxLoT@ainazi> > Content-Type: text/plain; charset=3D"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=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, > > > > 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. > > > > Language details: > > > > 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, > Iran, > > and the UAE > > > > Coordinator contact: > > > > Name: Hammad > > Email: [email protected] > > > > 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). > > > > Thank you, > > Hammad > > [email protected] > > > > > > > ------------------------------ > > Subject: Digest Footer > > _______________________________________________ > kde-i18n-doc mailing list > [email protected] > https://mail.kde.org/mailman/listinfo/kde-i18n-doc > > > ------------------------------ > > End of kde-i18n-doc Digest, Vol 276, Issue 1 > ******************************************** > --0000000000007f0a56064bf98b07 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable <div dir=3D"ltr"> <p class=3D"gmail-isSelectedEnd"><span>Thank you for the clarification.</sp= an></p><p class=3D"gmail-isSelectedEnd"><span>Understood: KDE on Linux reli= es on glibc locales for language selection.</span></p><p class=3D"gmail-isS= electedEnd"><span>I will work on creating a glibc locale first ( brh_PK.UTF= -8),=C2=A0 and then submitting it upstream to glibc.</span></p><p class=3D"= gmail-isSelectedEnd"><span>Two quick questions so I follow the right path:<= /span></p><ol start=3D"1"><li><p class=3D"gmail-isSelectedEnd"><span>Once a= glibc locale exists (brh_PK.UTF-8), is that sufficient for KDE to add/enab= le the Brahui translation team, or or are there other prerequisites before = you can proceed?</span></p></li><li><p class=3D"gmail-isSelectedEnd"><span>= Do you recommend starting with one locale only (brh_PK) first, and consider= ing additional region variants later (e.g., Afghanistan/Iran) only if neede= d?</span></p></li></ol><p><span>Thanks again,</span><br><span>Hammad</span>= <br><br></p> <br></div><br><div class=3D"gmail_quote gmail_quote_container"><div dir=3D"= ltr" class=3D"gmail_attr">On Sun, 1 Mar 2026 at 17:00, <<a href=3D"mailt= o:[email protected]">[email protected]</a>> wrote:= <br></div><blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8= ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">Send kde-i18n-d= oc mailing list submissions to<br> =C2=A0 =C2=A0 =C2=A0 =C2=A0 <a href=3D"mailto:[email protected]" target= =3D"_blank">[email protected]</a><br> <br> To subscribe or unsubscribe via the World Wide Web, visit<br> =C2=A0 =C2=A0 =C2=A0 =C2=A0 <a href=3D"https://mail.kde.org/mailman/listinf= o/kde-i18n-doc" rel=3D"noreferrer" target=3D"_blank">https://mail.kde.org/m= ailman/listinfo/kde-i18n-doc</a><br> or, via email, send a message with subject or body 'help' to<br> =C2=A0 =C2=A0 =C2=A0 =C2=A0 <a href=3D"mailto:[email protected]"= target=3D"_blank">[email protected]</a><br> <br> You can reach the person managing the list at<br> =C2=A0 =C2=A0 =C2=A0 =C2=A0 <a href=3D"mailto:[email protected]" t= arget=3D"_blank">[email protected]</a><br> <br> When replying, please edit your Subject line so it is more specific<br> than "Re: Contents of kde-i18n-doc digest..."<br> <br> <br> Today's Topics:<br> <br> =C2=A0 =C2=A01. Request: New KDE translation team for Brahui (brh) /<br> =C2=A0 =C2=A0 =C2=A0 =D8=A8=D8=B1=D8=A7=DB=81=D9=88=D8=A6=DB=8C (Hammad)<br= > =C2=A0 =C2=A02. Re: Request: New KDE translation team for Brahui (brh) /<br= > =C2=A0 =C2=A0 =C2=A0 =D8=A8=D8=B1=D8=A7=DB=81=D9=88=D8=A6=DB=8C (Shinjo Par= k)<br> <br> <br> ----------------------------------------------------------------------<br> <br> Message: 1<br> Date: Sun, 1 Mar 2026 01:26:09 +0500<br> From: Hammad <<a href=3D"mailto:[email protected]" target=3D"_blank"= >[email protected]</a>><br> To: <a href=3D"mailto:[email protected]" target=3D"_blank">kde-i18n-doc@= kde.org</a><br> Subject: Request: New KDE translation team for Brahui (brh) /<br> =C2=A0 =C2=A0 =C2=A0 =C2=A0 =D8=A8=D8=B1=D8=A7=DB=81=D9=88=D8=A6=DB=8C<br> Message-ID:<br> =C2=A0 =C2=A0 =C2=A0 =C2=A0 <CALoFT+6KQb3PnJ_AS02=3DOJhV8J5AcP=3D<a href= =3D"mailto:[email protected]" target=3D"_blank">KkuB9zK9oF= [email protected]</a>><br> Content-Type: text/plain; charset=3D"utf-8"<br> <br> =C2=A0Hello KDE i18n team,<br> <br> I would like to start a KDE translation team for the Brahui language, as I<= br> could not find an existing Brahui team on KDE=E2=80=99s translation teams l= ist.<br> <br> Language details:<br> <br> English name: Brahui<br> Native name (UTF-8): =D8=A8=D8=B1=D8=A7=DB=81=D9=88=D8=A6=DB=8C<br> ISO 639-1: (none)<br> ISO 639-2: (none)<br> ISO 639-3: brh<br> Primary script: Arabic-based script (RTL)<br> Also used: Latin orthography known as =E2=80=9CBrolikva / Brahui Roman Likv= ar=E2=80=9D (I<br> propose starting with Arabic-script RTL.<br> Regional usage: primarily Pakistan, also communities in Afghanistan, Iran,<= br> and the UAE<br> <br> Coordinator contact:<br> <br> Name: Hammad<br> Email: <a href=3D"mailto:[email protected]" target=3D"_blank">hammadalo= [email protected]</a><br> <br> Please advise the correct next steps to create/enable the Brahui team and<b= r> begin translation work (tools/workflow, where to submit translations, and<b= r> any requirements for team setup).<br> <br> Thank you,<br> Hammad<br> <a href=3D"mailto:[email protected]" target=3D"_blank">hammadalo99@gmai= l.com</a><br> -------------- next part --------------<br> An HTML attachment was scrubbed...<br> URL: <<a href=3D"http://mail.kde.org/pipermail/kde-i18n-doc/attachments/= 20260301/fc3ac5db/attachment-0001.htm" rel=3D"noreferrer" target=3D"_blank"= >http://mail.kde.org/pipermail/kde-i18n-doc/attachments/20260301/fc3ac5db/a= ttachment-0001.htm</a>><br> <br> ------------------------------<br> <br> Message: 2<br> Date: Sat, 28 Feb 2026 22:01:23 +0100<br> From: Shinjo Park <<a href=3D"mailto:[email protected]" target=3D"_blank"= >[email protected]</a>><br> To: <a href=3D"mailto:[email protected]" target=3D"_blank">kde-i18n-doc@= kde.org</a><br> Subject: Re: Request: New KDE translation team for Brahui (brh) /<br> =C2=A0 =C2=A0 =C2=A0 =C2=A0 =D8=A8=D8=B1=D8=A7=DB=81=D9=88=D8=A6=DB=8C<br> Message-ID: <5972745.DvuYhMxLoT@ainazi><br> Content-Type: text/plain; charset=3D"utf-8"<br> <br> Hello,<br> <br> It seems that there is no glibc locale yet for brh. Without glibc locale, <= br> there will be no locale to select the KDE software's language translati= on. <br> This has been discussed previously several times, see e.g. https://<br> <a href=3D"http://mail.kde.org/pipermail/kde-i18n-doc/2025-February/002662.= html" rel=3D"noreferrer" target=3D"_blank">mail.kde.org/pipermail/kde-i18n-= doc/2025-February/002662.html</a> for how to <br> proceed with glibc first.<br> <br> Best,<br> Shinjo<br> <br> 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:<br> >=C2=A0 Hello KDE i18n team,<br> > <br> > I would like to start a KDE translation team for the Brahui language, = as I<br> > could not find an existing Brahui team on KDE=E2=80=99s translation te= ams list.<br> > <br> > Language details:<br> > <br> > English name: Brahui<br> > Native name (UTF-8): =D8=A8=D8=B1=D8=A7=DB=81=D9=88=D8=A6=DB=8C<br> > ISO 639-1: (none)<br> > ISO 639-2: (none)<br> > ISO 639-3: brh<br> > Primary script: Arabic-based script (RTL)<br> > Also used: Latin orthography known as =E2=80=9CBrolikva / Brahui Roman= Likvar=E2=80=9D (I<br> > propose starting with Arabic-script RTL.<br> > Regional usage: primarily Pakistan, also communities in Afghanistan, I= ran,<br> > and the UAE<br> > <br> > Coordinator contact:<br> > <br> > Name: Hammad<br> > Email: <a href=3D"mailto:[email protected]" target=3D"_blank">hamm= [email protected]</a><br> > <br> > Please advise the correct next steps to create/enable the Brahui team = and<br> > begin translation work (tools/workflow, where to submit translations, = and<br> > any requirements for team setup).<br> > <br> > Thank you,<br> > Hammad<br> > <a href=3D"mailto:[email protected]" target=3D"_blank">hammadalo99= @gmail.com</a><br> <br> <br> <br> <br> <br> <br> ------------------------------<br> <br> Subject: Digest Footer<br> <br> _______________________________________________<br> kde-i18n-doc mailing list<br> <a href=3D"mailto:[email protected]" target=3D"_blank">kde-i18n-doc@kde.= org</a><br> <a href=3D"https://mail.kde.org/mailman/listinfo/kde-i18n-doc" rel=3D"noref= errer" target=3D"_blank">https://mail.kde.org/mailman/listinfo/kde-i18n-doc= </a><br> <br> <br> ------------------------------<br> <br> End of kde-i18n-doc Digest, Vol 276, Issue 1<br> ********************************************<br> </blockquote></div> --0000000000007f0a56064bf98b07--