Comment 6 for bug 290589

Revision history for this message
Martin Pitt (pitti) wrote :

I agree that this is worth fixing.

However, the new string needs to be i18n'ed with gettext. I. e. it needs to be wrapped into _(), and po/POTFILES.in needs to have that file. Also, I'm not sure how that works together with KDE's slightly uncommon l10n package structure. So it would really be best to discuss/fix this upstream first, and then backport to intrepid, so that we don't introduce a different string than upstream.

Maybe there is an already existing error message which would fit there, which is already i18n'ed and avoids introducing a new user visible string?