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

List:       kde-i18n-doc
Subject:    Re: [kde-francophone] kinfocenter.po : bug report #157387
From:       Albert Astals Cid <aacid () kde ! org>
Date:       2008-03-24 16:28:06
Message-ID: 200803241728.06397.aacid () kde ! org
[Download RAW message or body]

A Dilluns 24 Març 2008, Anne-Marie Mahfouf va escriure:
> Le Monday 24 March 2008 01:29:30 pm Pino Toscano, vous avez écrit :
> > Alle lunedì 24 marzo 2008, Anne-Marie Mahfouf ha scritto:
> > > Le Monday 24 March 2008 12:34:17 pm Pino Toscano, vous avez écrit :
> > > > Alle lunedì 24 marzo 2008, Anne-Marie Mahfouf ha scritto:
> > > > > > http://bugs.kde.org/show_bug.cgi?id=157387
> > > > >
> > > > > I'm on it. It's only 1 string, right? I got a bit confused with
> > > > > your message...
> > > >
> > > > Next time, please ask before fixing strings in the stable branch.
> > > > After all, it was just a '.' more, not even a real typo.
> > >
> > > What do yo mean? That it's not worth to be fixed in branch?
> > >
> > > This is so difficult to manage! I want to fix bugs and make KDE better
> > > and in the end I always end up being told that branch is frozen.
> > >
> > > I think in the end I'd better stop trying to help with all that. I
> > > reverted and reopened the bug report.
> >
> > Come on, do not turn that into a greek tragedy for nothing.
>
> Women tend to do that unfortunately!
>
> > Branch has always a freeze policy on the strings, and you know that.
> > Most probably other translators would had nothing against it, but as
> > there actually _is_ a policy for that, let's respect it and kindly ask
> > first.
>
> I don't know it, it's anti-natural for me not to fix things 

You can always fix them on trunk.

> and I keep 
> committing in branch. It's been already a few times that I forgot this
> policy.

Then you know now. Stable branch is always frozen for string changes. 
Otherwise translators can't work on stable texts.

The other reason is that i prefer to have a small non misleading typo on 
english text and 60 translated versions of that text than a fixed english 
text and 0 untranslated versions (remember each time you modify the original 
the translations are marked as fuzzy and someone has to go over them to mark 
them as ok)

> Was there a time when it was possible to fix such strings for 4.0.3 then?

No, as said, stable branch is always frozen for string changes, if you want 
you can mail this list and ask for an exception, and i can't remember last 
time we rejected such an request when it was sensible enough.

>
> > I personally refrained myself to fix just really easy typos like this in
> > stable branch in the past.
>
> So when are they fixed?

They are fixed on trunk and if you get the exception on the stable branch too, 
but unless it's a huge and misleading typo i'd fix it on trunk only.

Albert

>
> > Ah, and I'm totally false (as you wrote in the commit log) that I'm
> > "upset" for that, I'm just making people remember about the policy.
>
> It's me who is upset, I know you are not.
>
> Anne-Marie



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