Re: KLocale plans (Re: KF5 Unit test results)

2012-11-04 Thread Chusslove Illich
[: Chusslove Illich :] While splitting out public methods dealing with translation from KLocale [...] For completeness, also the overview of what I do with other methods (no comment needed except for objections :): All translateRaw*() methods are removed. They were used only by

Re: KLocale plans (Re: KF5 Unit test results)

2012-10-24 Thread David Faure
On Sunday 16 September 2012 19:22:26 Chusslove Illich wrote: [: David Faure :] Anyhow, I recommend splitting in place (in kdecore), first, to have commits that do the splitting, separated from the commits that do the moving. I can even do the moving once you've done the API splitting :-)

Re: KLocale plans (Re: KF5 Unit test results)

2012-09-16 Thread Chusslove Illich
[: David Faure :] Anyhow, I recommend splitting in place (in kdecore), first, to have commits that do the splitting, separated from the commits that do the moving. I can even do the moving once you've done the API splitting :-) Well that's totally great. I was thinking of asking about doing

Re: KLocale plans (Re: KF5 Unit test results)

2012-09-13 Thread David Faure
On Tuesday 11 September 2012 13:15:37 Chusslove Illich wrote: [: David Faure :] Is it also part of your plans to remove i18n()'s dependency on KLocale? I consider it rather an orthogonal matter. I will anyway remove all Gettext- related stuff from KLocale, before doing anything about

Re: KLocale plans (Re: KF5 Unit test results)

2012-09-11 Thread Chusslove Illich
[: David Faure :] Is it also part of your plans to remove i18n()'s dependency on KLocale? I consider it rather an orthogonal matter. I will anyway remove all Gettext- related stuff from KLocale, before doing anything about replacing *gettext() calls themselves. This is what's blocking me now,

KLocale plans (Re: KF5 Unit test results)

2012-09-10 Thread David Faure
On Wednesday 05 September 2012 10:48:54 Chusslove Illich wrote: Next I plan to rewrite klocalizedstring.h, such that it reflects the planned changes, but most importantly to have more comprehensive doc appropriate for a standalone component. After we review it, I go adapting the code.