On Sunday, August 14, 2011 06:47:13 am Jacek Kałucki wrote: > Użytkownik Paul McNett napisał: > > Reverted r6494 since it re-broke some of my customers' field decoding. > > Not sure what to do to resolve all cases, Jacek, but I think the > > condition needs to be different. > > Hi. > > Unfortunately, this commit broke my code, however dCursorMixin code works, > because of its string encoding conversion method, all dDataSet based > code has gone. > This leads me to conclusion I have to keep local versions of these files. > I think that using str as text factory isn't good for Dabo localization > and is begging for trouble it the future: > 1) sqlite developers strongly recommends using of unicode with it > 2) when using str factory, all strings are persisted with encoding they are > passed to, in effect you can't read them correctly after application > encoding switching or in different environments > 3) we should avoid forth and back unicode to str conversions for > performance reasons. I'm concious that any change in such vital code my > leads to problem with existing applications, but rolling problem forward > isn't a good solution too. My opinion is, let the bad things happen sooner > than later, but it's only mine.
Where does the '_' come in to play? I always thought that "_" handled the problem within DAbo. Johnf _______________________________________________ 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]
