<div dir="ltr"><div class="gmail_default" style="font-family:times new roman,serif">Why don`t use git for it or add weblate serve for syncronise?</div></div><br><div class="gmail_quote gmail_quote_container"><div dir="ltr" class="gmail_attr">сб, 6 сент. 2025 г. в 16:16, Karl Ove Hufthammer <<a href="mailto:karl@huftis.org">karl@huftis.org</a>>:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">Johnny Jazeix skreiv 25.08.2025 22:43:<br>
> If you are a summit user:<br>
> * which tool do you use?<br>
<br>
For Norwegian Nynorsk (nn), Norwegian Bokmål (nb) and Northern Sami <br>
(se), we use a simple Bash script:<br>
<br>
<a href="https://websvn.kde.org/trunk/l10n-support/nn/skript/kde-l10n-synk.sh?view=markup" rel="noreferrer" target="_blank">https://websvn.kde.org/trunk/l10n-support/nn/skript/kde-l10n-synk.sh?view=markup</a><br>
<br>
This also uses some custom Pology scripts to the merging:<br>
<br>
<a href="https://websvn.kde.org/trunk/l10n-support/nn/summit/messages.extras.summit?view=markup" rel="noreferrer" target="_blank">https://websvn.kde.org/trunk/l10n-support/nn/summit/messages.extras.summit?view=markup</a><br>
<br>
It uses a special helper script with some non-standard posieve options:<br>
<br>
<a href="https://websvn.kde.org/trunk/l10n-support/scripts/summit_helpers_NO.py?&view=markup" rel="noreferrer" target="_blank">https://websvn.kde.org/trunk/l10n-support/scripts/summit_helpers_NO.py?&view=markup</a><br>
<br>
<br>
> * What are the pros/cons of your tool?<br>
<br>
It’s completely automatic, i.e. it downloads the latest changes, merging <br>
in templates changes and commits the updated files. It automatically run <br>
‘svn add’ and ‘svn delete’ on new/removed local files.<br>
<br>
One nice feature is that it can operate in both fast and slow mode. In <br>
slow mode, it just adds the ‘--force’ argument to posieve, which make it <br>
(re)process *all* files and strings, e.g., adding new suggestions from <br>
the compendium and rewrapping all strings. (Usually, I use the fast mode.)<br>
<br>
The helper script also does some nice stuff. First, it uses a (large, <br>
local and specially prepared) compendium when merging the files, so that <br>
we get good fuzzy messages. It also adjusted the string similarity <br>
threshold, so that we can get suggestions for more strings.<br>
<br>
And it uses markup-based line-wrapping, which makes the files much <br>
easier to edit by the translators. This is basically the same as <br>
‘porewrap --no-wrap --fine-wrap’:<br>
<br>
<a href="http://pology.nedohodnik.net//doc/user/en_US/ch-common.html#sec-cmwrap" rel="noreferrer" target="_blank">http://pology.nedohodnik.net//doc/user/en_US/ch-common.html#sec-cmwrap</a><br>
<br>
It removes all obsolete messages from the non-summit files (with the <br>
summit workflow, they’re not needed, as we never edit the non-summit <br>
files manually), and clean up the PO file headers.<br>
<br>
Finally, it does a few search and replace operations that are <br>
appropriate for Norwegian.<br>
<br>
Cons: It’s not designed to be very robust. If you abort the operation <br>
(or posieve crashes), you have to manually run ‘svn cleanup’ (and <br>
perhaps ‘svn revert’ on a few folders).<br>
<br>
<br>
> * can we agree to use one common tool for all the languages and<br>
> enforce it in KDE?<br>
<br>
Yes, that would be nice. But would have to support language-specific <br>
(Pology) helper scripts.<br>
<br>
Is it supposed to run locally or on the server? If it’s on the server, I <br>
would miss the ability to use my local compendium (which also includes <br>
strings from various non-KDE applications that I have translated).<br>
<br>
<br>
-- <br>
Karl Ove Hufthammer<br>
</blockquote></div><div><br clear="all"></div><br><span class="gmail_signature_prefix">-- </span><br><div dir="ltr" class="gmail_signature"><div dir="ltr"><font face="comic sans ms,sans-serif">Wodsfort</font></div></div>