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

List:       kde-i18n-doc
Subject:    Re: Weather conditions - some proposals
From:       "Anne-Marie Mahfouf" <annemarie.mahfouf () free ! fr>
Date:       2009-07-21 8:48:30
Message-ID: 200907211048.30494.annemarie.mahfouf () free ! fr
[Download RAW message or body]

Hi,

The Weather Applet strings addition were added late and approved by some 
translators I think. For those who cannot translate them, it won't be worse 
than if they never were put in anyway and you won't suffer from stastistics 
because of them. 

The other added string was from a Ruby binding as bindings are not frozen at 
this point. Not sure if this is allowed or not.

I think it is time to draw some conclusions from this release and to make 
things better for the 4.4 release.

Personally the conclusions I make are:
1) Reinforce the i18n review for all kdereview programs. Before joining a KDE 
module, programs from playground go to kdereview (that's a trunk module) for 2 
weeks and should be reviewed. Few people know this and while we have 
developers dedicated in checking i18n it would be good that more people get 
involved.
Proposal: CC this list when a program goes to kdereview (only kde-core-devel 
is mailed)
Checking large pieces of code such as GSoC which do not go through kdereview 
is another problem. Make mentors aware of i18n importance by CCing this list 
when new big code is added so we can check strings.
2) Use one of the first beta to really check KDE in your translated language. 
Yesterday I found several bugs not due to the translation itself but to the 
code. For example the converter applet assumes 'square meters' but in French 
we translate to 'meters to square'. The translation of this applet to French 
is unusable.
Proposal: make a l10n-oriented pre-release (i.e. enforce the need of a check 
in translate languages to detect untranslated strings, bad formatted strings, 
layout problems, ...)

I feel that translators really express themselves by asking for more 
precisions about strings and that the ki18n strings formatting improved 
translators life a lot as well as Lokalize. Meanwhile as KDE spreads 
translations are more and more needed. The short release cycle maybe also is a 
difficulty to achieve perfection.

Do we have people from this list who are subscribe to the release-team mailing 
list? If not, I encourage you to do so. If you feel my proposals make sense I 
can convey them to the release team.
https://mail.kde.org/mailman/listinfo/release-team

Best regards to all and "bravo" for your achievement!

Anne-Marie

Le mardi juillet 21 2009 10:10:16 AM, Frank Weng (a.k.a. Franklin) a 
écrit :
> 在 2009 年 07 月 21 日 星期二 14:35:50，Thomas Reitelbach 寫道:
> > Am Dienstag, 21. Juli 2009 03:05:30 schrieb Frank Weng (a.k.a. Franklin):
> > > I finally made it...  *sweat*  I'm just wondering that if KDE 4.3.0 was
> > > scheduled to release on July 28th, why the strings were not freezed? 
> > > Is the release schedule delayed?  When is KDE 4.3.0 tagging?  I could
> > > still see string changes yesterday.
> >
> > KDE 4.3.0 is scheduled for tagging today and it is frozen in
> > branches/stable since ... *hm* May 5th.
> >
> > If you see string changes, then it's probably in trunk, but trunk is not
> > KDE 4.3 anymore.
>
> No, not in trunk.  I'm sure it's in stable.
> Even just now the kdepim/akregator in stable changed a string about
> copyright. (entry 116, (c) 2004-2009 Akregator developers).
> That's why I was curious about 4.3 string freeze day...
>
> > Here you can find the KDE release schedule:
> > http://techbase.kde.org/Schedules/KDE4/4.3_Release_Schedule
>
> I know this, but no messages should have been freezed on May 5, and weather
> conditions added nearly 700 entries a few days ago...
>
> > Cheers
> > Thomas
>
> Thanks,
> Franklin



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