On Wednesday 10 July 2013 13:30:17 Chusslove Illich wrote: > > [: Kevin Ottens :] > > For locale it should be QLocale really. KLocale is likely to disappear at > > some point. QLocale might not fulfill all your needs yet, but we'd need to > > know what you miss sooner than later. > > I don't have in mind anything in particular here. If a locale provider is > good enough for KDE software in general, then it is good enough for ki18n. I > would put it the other way around: *if* there will exist KLocale, then it > should do something above QLocale for KDE in general, and then ki18n should > use it too.
Well, the current situation is that KLocale is pretty much on the way out. There's still some areas which use it, but that's not for too much longer. > > Regarding the config provider, what use do you have for it in ki18n? > > There is already an ad-hoc, custom config solution in the Transcript plugin, > by which scripting can be influenced (on per-language basis). I'd also like > to enable some more debugging functionality for scripting, which would be > controlled through config. Maybe I will have more ideas. I don't remember > why I didn't use KConfig here in the first place, and now is as good moment > as any to get rid of this custom config solution. Well, if that's simple and used in the transcript plugin mostly I don't mind the ad hoc solution. Maybe keep the status quo there? Regards. -- Kévin Ottens, http://ervin.ipsquad.net Sponsored by BlueSystems and KDAB to work on KDE Frameworks
signature.asc
Description: This is a digitally signed message part.
_______________________________________________ Kde-frameworks-devel mailing list Kde-frameworks-devel@kde.org https://mail.kde.org/mailman/listinfo/kde-frameworks-devel
