>-----Original Message----- >From: meego-dev-boun...@meego.com [mailto:meego-dev-boun...@meego.com] On >Behalf Of Thiago Macieira >Sent: Monday, January 24, 2011 8:49 AM >To: meego-dev@meego.com >Subject: Re: [MeeGo-dev] Dconf > >Em segunda-feira, 24 de janeiro de 2011, às 16:38:46, Dave Neary escreveu: >> Arjan van de Ven wrote: >> > Heck, app writers wouldn't even notice the difference if you use the >> > proper abstraction API. >> >> ... which is, presumably, GSettings? > >Or a revamped QSettings if we can make it. > >Besides, the whole point is not to access the same file format, but to >access the same settings. This requires searching for the same keys, >accepting the same values. > >A good example is the locale configuration. On GNOME, it's configured >somewhere in GConf or DConf. In KDE, it's configured in >$KDEHOME/share/config/kdeglobals. >On MeeGo, I have no clue where it's supposed to be configured, given the >different implementations between netbook and the others. > >Of course, Qt doesn't integrate with any of those. The only way to >configuyre the locale in Qt is via the common denominator: the POSIX >configuration (by setting LANG and the LC_* variables). Unfortunately, none >of the environments set LANG to a file containing their settings[*], so the >common denominator is actually often the wrong config. > >Now, if we can get an agreement on where the setting should be (blessed by >XDG), then we'll be happy to read it from QtCore. > >[*] Qt doesn't read custom locale files yet, but we might just write that >code if MeeGo uses it. This doesn't require XDG blessing.
Again I ask--how does this affect localization? I still do not understand how I can change locale in MeeGo. Margie _______________________________________________ MeeGo-dev mailing list MeeGo-dev@meego.com http://lists.meego.com/listinfo/meego-dev
