>You mean total unicodization? As far as I understand it's not >incompatibilities that hold this change but complexity. The problem is >not localized to just templates filters it would be the change across >entire code.
Yep, it would be just a pain to do - loads of places need changing, all str() calls need to change over to unicode() and all boundaries need to "do the right thing" - like encoding to DEFAULT_ENCODING (http responses) or DATABASE_ENCODING (sql commands). It's definitely doable, and I think it would be worth to do. But I would prefer some comment from the core devs wether they want it, since it's not something that's on the stuff for version 1 :-) So maybe Adrian and Jacob could comment on wether they think this should be done pre-1.0, and if yes, I could dig in and try to do it in magic-removal. The patch to #914 is just sitting there because there is no comment from the core devs on it - but I think we should do either the unicodefication or the patch from #914, with my preference being the unicodefication. bye, Georg
