[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-i18n-doc
Subject:    Re: Fwd: branches/stable/l10n-kde4
From:       Vít Pelčák <vit () pelcak ! org>
Date:       2010-06-29 7:02:51
Message-ID: AANLkTimS8t6U9Mxl9IjG-jaYrGnZaffB-mMiviquRj6b () mail ! gmail ! com
[Download RAW message or body]

If I were you, I'd wait for few days until dust settles down and then
start Summit.

http://techbase.kde.org/Localization/Workflows/PO_Summit

It helps you keep stable and trunk pretty well in sync and you don't
have to care which branch you are translating.

2010/6/29 Ozan Çağlayan <ozan@pardus.org.tr>:
> Salı 29 Haziran 2010 günü (saat 01:26:19) Albert Astals Cid şunları yazmıştı:
>> A Dilluns, 28 de juny de 2010, Ozan Çağlayan va escriure:
>
>>
>> But i sincerely think you are doing it wrong by translating trunk and
>> backporting to stable since trunk (from today on) is what is going to be
>> KDE SC 4.6 so it's going to suffer a lots of changes soon, and most
>> probably there will be messages present in stable for KDE SC 4.5 that will
>> not be in trunk so backporting will not translate them and you will end up
>> with untranslated messages in the stable version.
>>
>
> You are right but there are still a lot of untranslated stuff in trunk for
> Turkish. Once you tag 4.x as stable, translations from trunk are merged to
> stable and a lot of translated and available in trunk strings stays within
> branches/4.(x-1). Unless we complete messages/kde*/ translations in trunk,
> this will always happen after every tagging.
>
> Maybe we should use lokalize's branch support and start committing to stable
> as well as trunk during trunk translation.
>
>
>
> ---
> Ozan Çağlayan
> TUBITAK/UEKAE - Pardus Linux
> http://www.pardus.org.tr/eng
>



-- 
Vit Pelcak

[prev in list] [next in list] [prev in thread] [next in thread]