Re: Getting mad with CGI::Application and utf8

[moritz] already pointed out that you shouldn't do _utf8_on. The :utf8 IO layer does the same thing and should also not be used. Using _utf8_on or :utf8 may result in serious malfunction and security holes.

Comment on Re: Getting mad with CGI::Application and utf8

Replies are listed 'Best First'.
Re^2: Getting mad with CGI::Application and utf8 by Anonymous Monk on May 15, 2008 at 18:37 UTC
There is another aproach: one i use from time to time. Dont use perls borken utf-8 support. Pass the Argument -C0 to perl at the head of your script , and perl will treat all strings as raw binary. As long as you only break your strings on well defined boundaries, and dont attempt to naively count characters, it will work fine. If you need to truncate a string at a certain arbitrary point, such as "100 bytes" or so, you will have to make sure it stops at a well defined UTF-8 endpoint.	[reply]

Replies are listed 'Best First'.

Re^2: Getting mad with CGI::Application and utf8
by Anonymous Monk on May 15, 2008 at 18:37 UTC

There is another aproach: one i use from time to time. Dont use perls borken utf-8 support. Pass the Argument -C0 to perl at the head of your script , and perl will treat all strings as raw binary. As long as you only break your strings on well defined boundaries, and dont attempt to naively count characters, it will work fine. If you need to truncate a string at a certain arbitrary point, such as "100 bytes" or so, you will have to make sure it stops at a well defined UTF-8 endpoint.

[reply]