Malcolm Tredinnick wrote: > > What I'd really like from you guys (Michael, Ivan, Gábor -- and anybody > else who wants to play along) is to see how the code fits in with your > existing workflow. What are the bits that are still hard for you? What > are the problems that aren't solved? I'm thinking about things like > Ivan's comment about file encodings when reading the templates. I wasn't > sure if it was an issue or not, Ivan brought it up more or less > immediately, which makes me think it's probably something to attach > slightly more priority to (particularly because it's easy to work with > in that case).
i'd like to know about Request objects... how "early" do you plan to switch to unicode? will request.GET/POST already contain unicode-keys + unicode-values? what about request.META? i would personally like to have GET/POST already contain unicode data. i am not sure about request.META. but because it can contain practically anything, i think it's better to leave it as byte-strings... > > We really need an East-Asian user in this loop, too. I have some > experience working in mixed Chinese/English and Japanese/English > workplaces, but nowhere near enough to be an expert on the trickier > problems that might come up. > i know a little japanese, and usually i am testing these django-unicode features/issues with japenese characters too, but i'm far from being a fluent/expert on japanese. do you have some specific issues you'd like to have tested in japanese or just generally? gabor --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django developers" 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/django-developers?hl=en -~----------~----~----~----~------~----~------~--~---
