From: Benny M. <ben...@gm...> - 2013-02-23 17:40:49
|
2013/2/23 John Ralls <jr...@ce...> > > On Feb 23, 2013, at 8:46 AM, Benny Malengier <ben...@gm...> > wrote: > > > > > 2013/2/23 John Ralls <jr...@ce...> > >> >> On Feb 22, 2013, at 10:52 AM, Benny Malengier <ben...@gm...> >> wrote: >> >> > Yes, good idea. >> > Do a beta 1. >> > No more new festures, only bug fixes. >> > People might think that beta means stable, and I do think Gramps no >> longer will eat your data. As Paul says, still crashes, but no new features >> should land, so beta is a good denomination. >> > >> >> Should I backport the locale changes to gramps40 before we release beta1? >> > > I did not follow the work in trunk. Can you briefly explain what advantage > it would bring to gramps40? > > > The advantages are largely for developers: Instead of 4 modules affecting > translation, there are only 2, and one of them, libtranslate.py, will be > consolidated in the next time I have some cycles to do so, leaving only > GrampsLocale. By providing a global locale object, there is no longer any > need to call the python locale module from elsewhere in Gramps code. That > abstraction facilitates the conversion to ICU, which provides better > sorting especially under MSWin, and more importantly allows multiple > localization objects so that when one runs a report in a language other > than the UI locale, the l10n can change as well as the translation. For an > example, if in Gramps40 I run a report in French, the dates will still be > formatted in the US MM/DD/YYYY, which would look pretty odd to most French > speakers. The consolidation of libtranslate.py will fix that. > > There are a few translation bugs that are fixed along the way. One that > comes to mind is the selection of the translated addons list, which in > Gramps40 can be confused by certain combinations of environment variables. > > The intended advantage for users was to provide a preference item for > language, since setting environment variables seems to be a constant source > of confusion. I haven't been able yet to figure out how the preference > system works -- due in large part to lack of time to study it -- so it > doesn't look like that will get done in time for beta1, which is feature > freeze if I understand correctly. > > Regards, > John Ralls > > > |