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

Kevin Kofler kevin.kofler at chello.at
Wed Nov 16 16:28:04 UTC 2011


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





--- Comment #70 from Kevin Kofler <kevin kofler chello at>  2011-11-16 16:28:04 ---
> 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.

> The problem is that fedora decided to apply this patch without knowing what it
> did and without taking into account you were using incosistent translations
> once KDE decided to stop distributing kde-qt.
[paragraph snipped and quoted / replied to separately below]
> This slip you had in fedora made us all lose lots of time trying to debug a
> problem none of us (except Fedora) were responsible of and most of us could
> never reproduce because we do not use fedora.

As per comment #64 and comment #65, this also affects (or affected) at least
Pardus and Slackware, which, to me, is also an indicator of a serious
communication breakdown. I don't think it's fair to put all the blame on
Fedora.

[the paragraph snipped from the above quote:]
> Next time you apply a patch it would be cool if you thought about the
> consequences of doing so and what must happen for it to work.

Our intention was the best, to continue to apply existing BUG FIXES to our Qt
packages rather than restoring the bugs they fixed. The fact that this i18n
patch slipped through was an unfortunate oversight. And yes, that was our
fault. But I still consider it KDE's fault that they stopped supporting their
bug fixes.

> I was expecting nothing after my comment but if anything I expected a thank you
> for explaining what the problem was and a commitment from your side to be more
> careful with patches in the future, but instead i find nothing else than an
> attempt to put the blame were it does not belong. And this makes me sad,
> because you always say you want to be a team player, but being a team player
> means accepting your own responsabilities, not trying to put them under the
> carpet.

Well, thank you for your help in debugging this!

But ultimately, if kde-qt hadn't been discontinued (I still think that was a
mistake; I'm also unhappy about those qt-copy patches in SVN which weren't
migrated to kde-qt in git for some reason; every dropped patch is likely to be
a bug coming back), or if the implications on translations had been discussed
on kde-packager, we wouldn't have had this problem in the first place.

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


More information about the kde-i18n-de mailing list