On Thu, Mar 6, 2008 at 4:36 PM, Jonathan LaCour <[EMAIL PROTECTED]> wrote: > > Ian Bicking wrote: > > > You can't get unicode even via **params. Encoded strings work > > okay, though. > > Duh... I didn't even think about this. That being said, I still > think that this is a largely irrelevant issue, as the developer can > ensure that they use ascii parameter names.
Well, sort of. The whole URL string is either unicode encoded or it's not. Fortunately the ASCI characters decode back to ASCI gracefully. So, we can document that params MUST be decodable to plain ASCI. This solves part of the problem, unless people really want unicode names. At which point TurboGears as it is would become unusable to them, since we always turn request params into params that we call in the function. I think the easy way out of that is to provide a switch that allows a user to specify that they don't want the params passed into their function at all. They should still be able to get at the validated params from the request object. I'd guess that this would be a project wide configuration option, though we could make yet another decorator to controll this on a per-exposed-method basis. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "TurboGears Trunk" 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/turbogears-trunk?hl=en -~----------~----~----~----~------~----~------~--~---
