Thanks for the fix. -Chris
On Mon, Feb 16, 2009 at 6:36 PM, Bruce Kroeze <[email protected]> wrote: > On Mon, Feb 16, 2009 at 12:51 PM, Jonathan <[email protected]> wrote: > >> >> I ran into the same problem this weekend, drove me absolutely nuts. I >> think in the last revision some language settings were changed. >> Rolling back a couple revisions fixed the issue for me. >> >> Jonathan >> > > I also ran into the bug, and I have a client which I can't delay so I just > went ahead and fixed it ... for now. > > I've just committed a new version [1961] which should be a lot more > resilient and obvious about what locales it is trying. If it fails, it will > show all the variations it tried, which should help your debugging. > > This is awkward and hard to manage code because the whole area is amazingly > complex to configure. It is very hard to deal with all the different OS and > development environments regarding languages without a huge cascading chain > of exception checking. So rather than add yet another two or three nested > exceptions, I've opted for an explicit list of locales to try. It works for > me, please let me know if it helps your situations too. > > Bruce Kroeze > http://gosatchmo.com > > > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Satchmo users" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/satchmo-users?hl=en -~----------~----~----~----~------~----~------~--~---
