From: "Jon Schutz" <jon+catal...@youramigo.com>
How would this patch affect systems that choose to encode their URLs in
something other than UTF-8? (Other character encodings are widely used,
particularly on Asian sites).
There might be a case for having the encoding type as a configurable
option (where one option is no decoding so the application can handle
it) - otherwise it has to be left to the application where the app
designers can reverse whatever encoding they have chosen.
**
Regarding the encoding, I think it could be helpful to be able to set a main
"encoding" config key in MyApp.pm and all the other modules check for it and
use it if it is set (templates, HTML::FormFu forms, config files, possibly
even DBIC classes). Those modules could use another encoding if this main
encoding type key is overwritten.
Octavian
_______________________________________________
List: Catalyst@lists.scsys.co.uk
Listinfo: http://lists.scsys.co.uk/cgi-bin/mailman/listinfo/catalyst
Searchable archive: http://www.mail-archive.com/catalyst@lists.scsys.co.uk/
Dev site: http://dev.catalyst.perl.org/
