No, we are not using Catalyst::Plugin::Unicode::Encoding
Dominic Germain --------------------------------------------- Administrateur réseau / Network administrator Sogetel www.sogetel.net [email protected] Le 12-02-15 à 22:25, Bill Moseley a écrit : > > > On Thu, Feb 16, 2012 at 9:51 AM, Dominic Germain <[email protected]> > wrote: > Hi, > > We just update from Catalyst 5.7.x to Catalyst 5.90007. > > All our apps code and our DBs are in ISO-8859-1 encoding. View::TT is > configured to output stuff as UTF-8 and everything is working fine until the > update. It means that there is some re-encoding occurring somewhere in > Catalyst View processing. > > Are you using Catalyst::Plugin::Unicode::Encoding? Are you decoding all > your templates and data on input? > > > > > The problem is quite simple: Catalyst is unable to figure out the right > content-length as soon we have characters that requires two bytes in UTF-8. > French accent characters like "é", "ê", 'è", "à", etc. are good examples. > Previously, "bytes::length" was used and it works fine but the code was > changed to just "length". > > Which is correct. length() on encoded content is the length in bytes. But, > if you are not encoding it will be wrong. > > > > -- > Bill Moseley > [email protected] > _______________________________________________ > List: [email protected] > Listinfo: http://lists.scsys.co.uk/cgi-bin/mailman/listinfo/catalyst > Searchable archive: http://www.mail-archive.com/[email protected]/ > Dev site: http://dev.catalyst.perl.org/
_______________________________________________ List: [email protected] Listinfo: http://lists.scsys.co.uk/cgi-bin/mailman/listinfo/catalyst Searchable archive: http://www.mail-archive.com/[email protected]/ Dev site: http://dev.catalyst.perl.org/
