Completely broken i18n in languagesupport+cpp

[Andreas Pakulat]

Hi,

the recent message for fixing QString-related krazy errors shows one
thing: 

The way languagesupport and cpp plugin use i18n is completely broken. It
assembles user visible text by translating individual words and putting
them together with possible values of variables.

This makes the text completely untranslatable as the translators have no
chance of translating the text properly.

I'll walk through the i18n calls in both in the next days, this is just
a friendly reminder to _not_ do that again or in other parts.

Andreas

-- 
You fill a much-needed gap.