Using Catalyst::Plugin::Unicode::Encoding instead of "hacking" Catalyst.pm works, but it brakes some other parts of our code (form posted containing some accent are screwed up).
Reverting Catalyst.pm to old fashion bytes::length() is way simpler... Anyone aware of drawback using it instead of length()? Dominic Germain --------------------------------------------- Administrateur réseau / Network administrator Sogetel www.sogetel.net mailingli...@sogetel.com Le 12-02-15 à 23:33, Bill Moseley a écrit : > > > On Thu, Feb 16, 2012 at 10:56 AM, Dominic Germain <mailingli...@sogetel.com> > wrote: > No, we are not using Catalyst::Plugin::Unicode::Encoding > > Does using it fix your problem? It should. But, you also should decode > input data, too. > > > > I'm still not sure why that is a separate plugin. When would you not need to > encode? Although, seems like should also check for the utf8 flag -- to catch > the case where the content has already been encoded. > > > -- > Bill Moseley > mose...@hank.org > _______________________________________________ > 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/
_______________________________________________ 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/
