Comment 9 for bug 1225099

ttx, dhellman and I discussed this a little on irc - conclusions:

1) We're not 100% sure what the user impact of this issue is, but we suspect it has the potential to be a critical issue for some users. Is it the case that a translation containing double-byte characters can basically render a service completely unusable?

2) Our fear is that the fix is complex enough such that there's a reasonable chance it's broken in some way

i.e. this is a critical issue and we don't have a huge amount of confidence that this fix resolves the issue without introducing further issues

That all suggests that we should disable lazy translation in all projects and revisit in Icehouse

This would involve removing the calls to gettextutils.enable_lazy() or gettextutils.install(lazy=True)

But we're eager to hear thoughts from folks more intimately familiar with the work - e.g. mrodden, luisg, bnemec, jswarren