Disappearing translations and maintaining consistency over branches

Edward Wornar edi.werner at gmx.de
Sun Nov 28 12:53:39 GMT 2021


Dnja 28.11.21 10:58:07 CET, Łukasz Wojniłowicz napisa:
> Hi Edward,
> 
> I suggest using and setting up properly Lokalize for that.
> In Lokalize I have two projects:
> 1) kf5-stable
> 2) kf5-trunk
> 
> File kf5-stable.lokalize contains:
> AltDir=./kde/trunk/l10n-kf5/pl
> BranchDir=./kde/trunk/l10n-kf5/pl
> PoBaseDir=./kde/branches/stable/l10n-kf5/pl
> PotBaseDir=./kde/branches/stable/l10n-kf5/templates
> 
> File kf5-trunk.lokalize contains:
> AltDir=./kde/branches/stable/l10n-kf5/pl
> BranchDir=./kde/branches/stable/l10n-kf5/pl
> PoBaseDir=./kde/trunk/l10n-kf5/pl
> PotBaseDir=./kde/trunk/l10n-kf5/templates
> 
> Notice that stable project points to the trunk branch, and trunk project
> points to the stable branch.
> 
> That way if I translate something in stable then it goes into trunk and
> in reverse. It happens automatically. Hope it will help you.

Thanks, that could actually be easier than the other approach which gave me a 
strange additional directory on my first tries.

> 
> Cheers
> Łukasz
> 
> 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