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

List:       kde-i18n-doc
Subject:    Re: IMPORTANT: moving towards KDE4 translations
From:       Stephan Kulow <coolo () kde ! org>
Date:       2007-02-28 11:59:13
Message-ID: 200702281259.14488.coolo () kde ! org
[Download RAW message or body]

Am Mittwoch 28 Februar 2007 schrieb Diniz Bortolotto:
> Sex 09 Fev 2007 Ã s 11:47, Stephan Kulow escreveu:

What does the word Sex mean in your language? :)

> > Hi!
> >
> > As noted earlier, the KDE modules in trunk/l10n are no longer used for
> > anything. The KDE4 translations will happen for the moment in another
> > branch, that is automatically generated from stable. So please feel free
> > to clean up trunk's PO files.
>
>
> Hi Stephan!
Hi Diniz!
>
> I'm in doubt on future new branch for KDE4.
>
> Will be it made merging kde4-l10n and current trunk or,
> kde4-l10n and stable?

stable: where I get the latest translations from
trunk: where the latest sources are
kde4-l10n: where the stable translations are merged against latest sources.
>
> If it will be made with trunk, why must we delete trunk's PO files and
> proceed with stable translation?
It won't be trunk/l10n as there are currently KDE3 translations and we can't 
mix them. As long as KDE3 is the majority of translators work, I won't 
exchange that path. It might end up in trunk/l10n-kde4 though.
>
> Otherwise, if it will be made with stable, the number of fuzzies and
> untranslated messages will be bigger.
> In this case, could we do commits like my commit 637300 to reduce
> untranslated messages? (old kopete.po with 77.37% translated and the new
> with 88.40%)
Yes, it should. 
A) it will improve KDE 3.5.X
B) it will be merged against latest sources - if those 11% will make a 
difference against latest kopete sources, I can't say, but I would guess it 
does.

Greetings, Stephan
[prev in list] [next in list] [prev in thread] [next in thread]