I'm currently working on tickets 1480, 1619 and 1842 (content type and encoding for TurboJson).
Though simplejson has some interesting options such as "ensure_ascii" and "encoding" (which sets the input encoding), TurboJson so far used only the default otions. I made these configurable in r4629 now. To make this work, the options must still be added to turbogears.view.base.load_engines. I'd like to get some feedback before doing this: * Do we want to make TurboJson configurable in TG 1.0 as well? * All options will get the same name as in simplejson, only prefixed with "json.". * Exception: "json.assume_encoding" instead of "encoding", similar to the Kid options, since "encoding" usually means the output encoding? * Default values for the options the same as in simplejson? * Exception: ensure_ascii=False instead of True, this will make non-enlgish json ouput much smaller and better readable? -- Christoph --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
