Summit workflow - git migration

[Johnny Jazeix]

Hi,

Le sam. 6 sept. 2025 à 15:24, Karl Ove Hufthammer <karl at huftis.org> a écrit :
>
> Johnny Jazeix skreiv 25.08.2025 22:43:
> > If you are a summit user:
> > * which tool do you use?
>
> For Norwegian Nynorsk (nn), Norwegian Bokmål (nb) and Northern Sami
> (se), we use a simple Bash script:
>
> https://websvn.kde.org/trunk/l10n-support/nn/skript/kde-l10n-synk.sh?view=markup
>
> This also uses some custom Pology scripts to the merging:
>
> https://websvn.kde.org/trunk/l10n-support/nn/summit/messages.extras.summit?view=markup
>
> It uses a special helper script with some non-standard posieve options:
>
> https://websvn.kde.org/trunk/l10n-support/scripts/summit_helpers_NO.py?&view=markup
>
>
> > * What are the pros/cons of your tool?
>
> It’s completely automatic, i.e. it downloads the latest changes, merging
> in templates changes and commits the updated files. It automatically run
> ‘svn add’ and ‘svn delete’ on new/removed local files.
>
> One nice feature is that it can operate in both fast and slow mode. In
> slow mode, it just adds the ‘--force’ argument to posieve, which make it
> (re)process *all* files and strings, e.g., adding new suggestions from
> the compendium and rewrapping all strings. (Usually, I use the fast mode.)
>
> The helper script also does some nice stuff. First, it uses a (large,
> local and specially prepared) compendium when merging the files, so that
> we get good fuzzy messages. It also adjusted the string similarity
> threshold, so that we can get suggestions for more strings.
>
> And it uses markup-based line-wrapping, which makes the files much
> easier to edit by the translators. This is basically the same as
> ‘porewrap --no-wrap --fine-wrap’:
>
> http://pology.nedohodnik.net//doc/user/en_US/ch-common.html#sec-cmwrap
>
> It removes all obsolete messages from the non-summit files (with the
> summit workflow, they’re not needed, as we never edit the non-summit
> files manually), and clean up the PO file headers.
>
> Finally, it does a few search and replace operations that are
> appropriate for Norwegian.
>
> Cons: It’s not designed to be very robust. If you abort the operation
> (or posieve crashes), you have to manually run ‘svn cleanup’ (and
> perhaps ‘svn revert’ on a few folders).
>
>
> > * can we agree to use one common tool for all the languages and
> > enforce it in KDE?
>
> Yes, that would be nice. But would have to support language-specific
> (Pology) helper scripts.
>
> Is it supposed to run locally or on the server? If it’s on the server, I
> would miss the ability to use my local compendium (which also includes
> strings from various non-KDE applications that I have translated).
>

At least locally. At long term, I think we can have a gitlab workflow
that will run once a day for each language that can do the job (if the
coordinator wants of course, it will be on voluntary base).
It would help the "non-tech" maintainers to have the workflow set up
and not bother with the tooling.

Your use case is more complex than the usual ones, so it may be harder
to automatize (especially with the local compendium), thanks for
providing it!

Cheers,

Johnny

>
> --
> Karl Ove Hufthammer