PerlScript and Localization

Lexicon has asked for the wisdom of the Perl Monks concerning the following question:

I am trying desperatly to enable reliable Japanese support into my Perlscript. Do any of you have experience with getting perl to play nicely with a 2-Byte character set under PerlScript in IIS? Currently, IIS does nothing short of completely freak out. Consider this code:

<%@ LANGUAGE = PerlScript %>
<html><body>
<%
use locale;
$Response->Write("English<p>");  # English
$Response->Write("“ú–{Śę<p>"  );  # Japanese (In Japanese)
%>
</body></html>
[download]

Most of you will see what Perl probably see...a bunch of line noise. I can leave the code alone, hit refresh, and Perl/IIS will generate different error values on different reloads. Usually it's a simple Syntax Error or </code>Cannot find string terminator '"'</code> but sometimes it will:

PerlScript Error Error:'80004005' 
(in cleanup) Unrecognized character \xBC 
example.asp, at Line 6
[download]

and sometimes, just for spite, it will work. ;-)

Perl and IIS are fine. If I take out the Japanese, I've no problems. Actually, if I put the Japanese inside of <%= “ú–{Śę %> it seems to work fine, but that is kind of limiting when I need to send e-mail. I've tried embedding the Japanese in HEREDOC, qq() and others. No luck. I'm tempted to try to start parsing it out of a file, but one can imagine how ugly that might become.

Thus I ask: I know PerlScript doesn't really support Japanese yet, but is there any reliable way I can force it to do so anyway?

NT Server 4.0 Service Pack 6 & IIS
ActiveState 5.6.0 Build 623 (5.6.1 636 is out. I might try that tomorrow)

-Lexicon

Comment on PerlScript and Localization Select or Download Code

Replies are listed 'Best First'.
Re: PerlScript and Localization by Lexicon (Chaplain) on May 11, 2001 at 10:49 UTC
Well, it wasn't what I was looking for, but this is the best solution I could find: sub UserError { my $msg = shift; my $serialcode = shift; my $email = shift; open JAPANERROR, $japanerrorfile or die "Can not open $japanerrorfile: $!"; my @JapanArray = <JAPANERROR>; close JAPANERROR or die "Can not close $japanerrorfile: $!"; chomp @JapanArray; my ($j_invalidcode, $j_badcodelength, $j_invalidemail, $j_expiredtrial, $j_unknownerror) = @JapanArray; $Response->Write("<html><body><h3>"); if ( $msg =~ /Bad code length/ ) { $Response->Write( "$j_badcodelength ($serialcode)" ) } elsif ( $msg =~ /Not a valid code/ ) { $Response->Write( "$j_invalidcode ($serialcode)" ) } elsif ( $msg =~ /Not a valid Email/ ) { $Response->Write( "$j_invalidemail ($email)" ) } elsif ( $msg =~ /You already used your 3 trial time/ ) { $Response->Write( "$j_expiredtrial ($email)" ) } else { $Response->Write( "$j_unknownerror" ) } $Response->Write("</h3></body></html>"); exit(1); } [download] And here's an example of the error file, not yet translated: `ERROR : Bad code length ERROR : Not a valid code ERROR : Not a valid Email ERROR : You already used your 3 trial time ERROR : Unknown Error` [download] -Lexicon	[reply] [d/l] [select]
Re: PerlScript and Localization by AidanLee (Chaplain) on May 10, 2001 at 18:52 UTC
I'm not sure how pragmas work in perlscript as opposed to normal perl, but perhaps a `use utf8` would clue the perl interpereter into what you are trying to do? Update Not that I think you're looking to go this far out of your way, but starting on page 276 of "Unicode: A Primer" by Tony Graham outlines unicode use in Perl (as of 5.005). I imagine the examples hold equally as well for Perl 5.6	[reply] [d/l]
Re: PerlScript and Localization by AgentM (Curate) on May 10, 2001 at 17:27 UTC
You might give quotemeta a try. Given all of the other stuff you've tried, it most likely will end up pumping out garbage, but it's at least worth a shot. AgentM Systems nor Nasca Enterprises nor Bone::Easy nor Macperl is responsible for the comments made by AgentM. Remember, you can build any logical system with NOR.	[reply]


Your skill will accomplish what the force of many cannot
	PerlMonks

PerlScript and Localization

AgentM Systems nor Nasca Enterprises nor Bone::Easy nor Macperl is responsible for the comments made by AgentM. Remember, you can build any logical system with NOR.