On Fri, Jul 12, 2013 at 1:02 PM, Lukas <lukas.vyslo...@gmail.com> wrote: > we are using Perl 5.10, Mason 1.42 and having an issues with UTF-8 encoded > strings. Recently we are accepting new customers from different countries > that have different letters in the database and standart encoding cannot > support this. From what Ive read, even if i encode string in one mason > component to UTF8 as soon as this string is passed to another component it > is again treated Lating1 event that the string was previously converted to > UTF8.
I haven't seen this behavior and it would be really odd, Mason would have to be explicitly taking a scalar that has the UTF-8 flag and removing it before passing it on. I haven't seen it do any such thing. Do you have some narrowed-down testcase that shows this issue. > this is causing huge problems for us. Is there a way how to enforce > UTF8 for every module? Unfortunately we cannot upgrade to higher > versions of perl or mason as our app would not work in this > environment. Wait this is related to the UTF-8 semantics changing in later perl or Mason versions? Seems to me you're 99% of the way to narrowing down your problem then, just bisect perl and/or Mason to see when the relevant change in behavior was introduced, or as it seems in your case, broken even further. ------------------------------------------------------------------------------ See everything from the browser to the database with AppDynamics Get end-to-end visibility with application monitoring from AppDynamics Isolate bottlenecks and diagnose root cause in seconds. Start your free trial of AppDynamics Pro today! http://pubads.g.doubleclick.net/gampad/clk?id=48808831&iu=/4140/ostg.clktrk _______________________________________________ Mason-users mailing list Mason-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/mason-users
