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 KLocalizedSt

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

2012-11-04 Thread Chusslove Illich
While splitting out public methods dealing with translation from KLocale, I got a doubt about localizedFilePath(). For a given file path, it returns the localized file path, if available, according to the same language list and fallback rules as for strings in PO files. Due to this, initially I tho

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

2012-10-27 Thread Chusslove Illich
> [: David Faure :] > Hi Chusslove, > > any progress? :-) No progress, but I'm going to do it right now. -- Chusslove Illich (Часлав Илић) signature.asc Description: This is a digitally signed message part. ___ Kde-frameworks-devel mailing list Kde-f

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 splitt

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 do

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

2012-09-16 Thread David Faure
On Saturday 15 September 2012 13:36:42 Chusslove Illich wrote: > > [: David Faure :] > > So either i18n is ported away from KLocale, or all that calendar stuff has > > to move into the ki18n framework, at least in the short term. > > Since including calendar stuff into ki18n would be a temporary m

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

2012-09-15 Thread Chusslove Illich
> [: David Faure :] > So either i18n is ported away from KLocale, or all that calendar stuff has > to move into the ki18n framework, at least in the short term. Since including calendar stuff into ki18n would be a temporary measure that would later have to be undone, I think it's best that I split

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 no

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. Water