[Repoze-dev] [issue100] Configurable character set support for repoze.who and repoze.what

Chris McDonough added the comment: I mean that I personally don't know how to change the software based on your suggestions so far in a way that adds significant value, and that if WSGI2 will handle the encoding and decoding issues, maybe this should just do something better with r.who then.

[Repoze-dev] [issue100] Configurable character set support for repoze.who and repoze.what

Yuen Ho Wong added the comment: I'm not entirely sure why this is not "actionable on any realistic level", and what you mean by lower layers. Perhaps you can explain further or point me to a previous discussion if this has been talked about before? -- status: resolved -> chatting _

[Repoze-dev] [issue100] Configurable character set support for repoze.who and repoze.what

Chris McDonough added the comment: I don't think this is actionable on any realistic level within our current implementation. This should be solved at lower layers. -- status: chatting -> resolved __ Repoze Bugs

Re: [Repoze-dev] Problem of showing Formish form in repoze.bfg

2009/10/24 Tres Seaver : > No, it works fine for values wich aren't markup:  if you want a variable > containing markup to be rendered without escaping, you need the > 'structure' directive in TAL:  the shortcut always escapes markup. Alternatively, wrap your ``addform`` value as a literal (``from