A first step might be to send a hardcoded utf-8 header. Then add the
config option.
If we use Cherrypys per-path config system we could easy set the
charset to different thing in different places in the app.
On 10/3/05, Kevin Dangoor <[EMAIL PROTECTED]> wrote:
>
> On 10/3/05, Elvelind Grandin <[EMAIL PROTECTED]> wrote:
> >
> > great!
> > Do we want a similair option for setting the charset header?
>
> That one's possibly trickier. At the moment, there are some hardcoded
> utf-8s in there. What's probably needed is a global setting (that goes
> in the config file) with the default encoding and use that to replace
> the utf8s and also send an appropriate charset. Are there people out
> there using more than one encoding on a single site? (I can certainly
> imagine it, but I don't want to implement a YAGNI.)
>
> Kevin
>
--
cheers
elvelind grandin
