Disappearing translations and maintaining consistency over branches

Frederik Schwarzer schwarzer at kde.org
Mon Nov 29 11:59:06 GMT 2021

On 11/28/21 10:58, Łukasz Wojniłowicz wrote:


> I suggest using and setting up properly Lokalize for that.
> In Lokalize I have two projects:
> 1) kf5-stable
> 2) kf5-trunk

I have been using Lokalize's sync feature for years and it worked like a 
charm. Then I learned about the plasma-lts branch 
(branches/stable/l10n-kf5-plasma-lts/) and all fell apart because I 
could not sync three branches. :(

So now we are using the summit workflow and it's fine as well. Just the 
time it takes to merge/scatter is a bit of a pain. On my laptop it takes 
about 15 to 20 minutes each (for both messages and docmessages).


> Dnia 2021-11-27, o godz. 10:48:35
> Edward Wornar <edi.werner at gmx.de> napisał(a):
>> Hello,
>> I have two maybe unrelated questions:
>> - Every once in a while, tranlations disappear when I install an
>> updated translation on my computer. I am aware that this is being
>> caused by changes in the source files. Often I can see the now for my
>> computer missing translations in the files, commented out. Since I
>> want to provide my translations for other users, how do I go about
>> this and prevent them from disappearing w.o. breaking anything?
>> Just a very concrete example, only yesterday the Sorbian translation
>> for kmail's submenu entries 'Mark message as important/Read/Unread'
>> have disappeared. (I have an up-to-date installation of KDE Neon.)
>> - Since it is mostly me doing all the translation work, I am
>> translating in the stable branch, but some bits are already there in
>> trunk. How do I get changes (e.g. terminology) I make in stable over
>> to trunk in the most efficient way?
>> Best
>> Edi

More information about the kde-i18n-doc mailing list