On 9/30/10 2:41 PM, Ed Leafe wrote: > On Sep 30, 2010, at 2:55 PM, Jacek Kałucki wrote: > >> I have many problems with Dabo localization. >> Most of them are result of mixed encoding declarations. >> I mean, some parts of code takes encoding setting directly >> from dabo.defaultEncoding variable, but other parts reads >> dApp.Encoding property instead, which is the simply shortcut >> to 'locale.getlocale()[1]'. >> How it works? > > > You have to remember that most encoding stuff has been added on to fix > problems that were discovered at various times; it wasn't as if a consistent > design was envisioned and carried out. > > Having said that, dApp respects the current setting of the locale > module if one has been set; otherwise, it uses dabo.defaultEncoding. Now that > you point out the inconsistency, I agree that all of these places where an > encoding value is accessed should get it from the same place. One problem, > though, is that self.Application is not always available, so it would > probably make more sense to create a "getEncoding()" method in the dabo > module level that does what dApp._getEncoding() does.
+1 Paul _______________________________________________ Post Messages to: [email protected] Subscription Maintenance: http://leafe.com/mailman/listinfo/dabo-dev Searchable Archives: http://leafe.com/archives/search/dabo-dev This message: http://leafe.com/archives/byMID/[email protected]
