From kde-release-team  Sun May 30 09:43:06 2010
From: Frederik Schwarzer <schwarzerf () gmail ! com>
Date: Sun, 30 May 2010 09:43:06 +0000
To: kde-release-team
Subject: Re: KDE SC 4.6 Schedule
Message-Id: <201005301143.06443.schwarzerf () gmail ! com>
X-MARC-Message: https://marc.info/?l=kde-release-team&m=127521263024862

[Albert Astals Cid - Sonntag 30 Mai 2010 11:04:59] 
> A Diumenge, 30 de maig de 2010, Sebastian Kügler va escriure:
> > On Sat May 29 2010 14:15:49 Albert Astals Cid wrote:
> > > > Thanks, I've put the schedule online now.
> > > 
> > > Found a little error, Soft Message Freeze says "Typo fixes can be fixed
> > > until  Beta2", but Hard Message Freeze does not kick in until 12 days
> > > after Beta2, can we change the text of Soft Message Freeze to say "Typo
> > > fixes can be fixed until Hard Message Freeze"?
> > 
> > I'm not much of a translator (not at all, in fact), but aren't typos
> > restricted to one language? And would the translated version still work
> > (but be "fuzzy")?
> > 
> > If those assumptions are true (translations aren't broken by fixing a typo,
> > but only marked as "have another look"), then I'd propose to just allow
> > typo fixes, whenever. If not, please educate me :D

> fuzzy effectively means untranslated, so no your suggestion is not valid.

...and to add some explanation. :)

Changes to the original string has to mark the translated string "fuzzy"
because gettext cannot see if you just fixed a typo or something that changed
the meaning. Furthermore a typo fix can change how a translater understands
and translates the string.

So after a typo fix, all translators have to check the string and "unfuzz"
it for it being shown in the UI again.

Regards
_______________________________________________
release-team mailing list
release-team@kde.org
https://mail.kde.org/mailman/listinfo/release-team