Hey all,
when updating some German translation of e17 trunk, I noticed that many
components still lack i18n. So I started updating many of them and
successfully introduced translations as I could verify on my computer.
As you may know, translations are an important step for software to be
spread
Sorry for this duplicate, Evolution is not working properly today :(
Am Donnerstag, den 06.01.2011, 19:38 +0100 schrieb Fabian Nowak:
> Hello,
>
> few weeks ago I obtained the message about e17 pre3 and tried it and was
> very impressed. However, when updating some translations,
Hello,
few weeks ago I obtained the message about e17 pre3 and tried it and was
very impressed. However, when updating some translations, I found some
un-i18n'ed components. Attached are the patches that should make them
translatable. I declared many DBG / ERR messages as translatable because
they
Hello,
few weeks ago I got note that e17 has taken enormous steps since I last
tried it out in 2008. So, i tried e17 and was deeply impressed.
Overhauling some translations, I noticed some components lack i18n
support. So attached you find patches to add i18n to some projects.
Besides, I needed mo
