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

List:       kde-i18n-doc
Subject:    Re: request to break string freeze, re bug 152883
From:       "=?UTF-8?Q?M=C4=81ris_Narti=C5=A1s?=" <maris.kde () gmail ! com>
Date:       2007-11-30 20:12:08
Message-ID: 9a4fa4b70711301212j547d96f4h2544db73594b6355 () mail ! gmail ! com
[Download RAW message or body]

Isn't it unfair to dissallow requested string changes, but allow silent ones:

http://websvn.kde.org/trunk/l10n-kde4/lv/messages/kdebase/libplasma.po?r1=742886&r2=743227
http://websvn.kde.org/trunk/l10n-kde4/lv/messages/kdebase/desktop_kdebase.po?r1=742886&r2=743227
and some others.

Just my 0.002 cents,
Maris.



2007/11/30, Thomas Reitelbach <tr@erdfunkstelle.de>:
> Am Donnerstag, 29. November 2007 21:50:31 schrieb Matthew Woehlke:
> > http://bugs.kde.org/show_bug.cgi?id=152883
> > Some people on IRC suggested this is severe enough to break string
> > freeze. What do the translators think?
> >
> > Note that this is not a functionality change compared to KDE3, which has
> > the same behavior (selecting a scheme silently replaces the "working
> > scheme" with that scheme; any unapplied or unsaved changes are silently
> > discarded).
> >
> > The new string would be something like "Changes to the current scheme
> > will be lost". (The "don't show this again" string already exists, of
> > course.)
>
> Well, the time is short until the release of KDE 4.
> I would prefer you wait for the release and make your changes afterwards.
> Then
> it is guaranteed to be in the next bugfix release.
>
> What do others think?
>
[prev in list] [next in list] [prev in thread] [next in thread]