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

List:       kde-i18n-doc
Subject:    Re: KDE3 release schedule reminder
From:       Rinse de Vries <rinse () kde ! nl>
Date:       2002-02-26 23:01:55
[Download RAW message or body]

This is OK with me, as long as the number of fuzzies doen't get as big as 500 
or so :)

Got a Off Topic Question:
the cvs directory
/home/kde/kdenetwork/kppp/DB/Provider/Netherlands/
contains several DB's of Dutch providers.
This week I have done a query among those providers and found that 95% of 
them uses new settings, so all files should be editted.
Is it Ok to proceed?
 

Op dinsdag 26 februari 2002 18:45, schreef Dirk Mueller:
> On Die, 26 Feb 2002, Dirk Mueller wrote:
> > - if possible no i18n-string changes.
>
> grmbl :-(
>
> You might know that we're currently together on a hacking meeting and we
> found many bugreports that require i18n string changes (because the GUI
> strings are unclear or misleading or simply wrong. Sometimes its only
> simple things like accelerator clashes etc).
>
> So the question is what to do with the i18n string freeze...
>
> Suggestion:
>
> - allow us to do i18n string changes till monday (RC1). You still have at
> least 1 week till 3.0 to resolve the fuzzies. We can also release updated
> kde-i18n packages as soon as you're finished with translating the release
> (which could give you additional 3-4 weeks).
>
> comments ?
>
>
> Dirk
[prev in list] [next in list] [prev in thread] [next in thread]