Re: SVN Workflow for Gujarati (gu)

Johnny Jazeix <[email protected]> Sun, 12 Apr 2026 09:43:11 +0200
Newsgroups gmane.comp.kde.devel.internationalization-and-documentation
Message-ID <CAEtcAPH6i5asXUEOiq1afT2Nj2V=d6XgdCz7N+KZ2Sm=XFb5zA@mail.gmail.com>
Hi,
You can find the templates of each file in
https://invent.kde.org/localization/l10n-templates.
The documentation for summit is
https://techbase.kde.org/Localization/Workflows/PO_Summit. Please note
that even if it is used by multiple teams, summit is not officially
supported by KDE.
For French, we use this script:
https://websvn.kde.org/trunk/l10n-support/fr/summit/scripts/sync_summit_bra=
nches.sh?view=3Dmarkup,
which will download the correct branches on the first run, then it
will merge/scatter and then generate the docbooks.
German team use Klash: https://invent.kde.org/bxela/klash which is a
collection of scripts to help with the summit flow.

Cheers,
Johnny

Le sam. 11 avr. 2026 =C3=A0 12:01, Crazy Court <[email protected]> a =
=C3=A9crit :
>
> Hello everyone,
>
> I=E2=80=99m starting on the Gujarati (gu) translation and noticed many pa=
ckages (like GCompris) are missing from trunk/l10n-kf6/gu/.
>
> I=E2=80=99ve reviewed the documentation on the Summit workflow and Script=
y automation but find the bootstrapping process for an inactive language st=
ructure confusing.
>
> To avoid breaking automation, should I initialize the l10n-support (Summi=
t) structure for gu first, or commit directly to the branches in l10n-kf6? =
Please guide or point me to the latest documentation for this specific setu=
p, Thank you.
>
> Best regards,
>
> Samyak Vidhan