[Bug 256591] kcalc German translation: using 2 on keyboard doesn't work

[Albert Astals Cid]

https://bugs.kde.org/show_bug.cgi?id=256591





--- Comment #71 from Albert Astals Cid <tsdgeos terra es>  2011-11-16 16:49:53 ---
> > This is in no way KDE's fault. KDE has always shipped tarballs that were
> > consistent. When this patch was in kde-qt, our translations took it into
> > account, when we stopped distributing kde-qt, our translations were changed > > and continued being correct.
> But nobody alerted us distributors of that change. The change affects not just
> our forward-ported kde-qt patches (which, incidentally, we had already dropped
> with 4.8 / Fedora 16, by the way), but also mixing existing kde-qt releases
> which you did ship with newer kde-l10n, or shipping newer Qt releases without
> your no longer supported kde-qt patches with older kde-l10n. This is exactly
> the kind of change which needs to be announced on kde-packager.

I don't think what you are asking is fair. I (as a programmer) am responsible
to ensure the tarballs I ship are correct, that's the end of my responsability.
You can not ask me to think of all the possible patches or not people may have
or may have not applied over my code and go saying, remember if you applied
patch A now you will have this problem. Enough problems I have as a programmer
to make sure my stuff is the most correct I can to have to care about every
possible patching combination people has done over my code.

I think that it is the people adding patches on top of my code that are
responsible for checking each time that I release a new version if those
patches still apply. And yes, I agree this is a very cumbersome and boring
process, and that is why i think there should not be any kind of distribution
patching other than backporting and security fixes (when it makes sense).

> I don't think it's fair to put all the blame on Fedora.
Right, my fault, the problem was not Fedora, the problem was the distributions
that were shipping the patch without knowing its consequences.

I agree it would have been awesome if I as the actual creator of the patch
would have thought on the issue an warned kde-packager. Would that would have
been a plus, not something you can demand from us, since if what you had done
was ship the tarballs we ship, there would have never been any problem.

-- 
Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.