Well, that's was an interesting comment by Martin - thanks! - but sounds
like he's saying you need to use a utility to convert to unicode for some
asian encodings and once you get it there you're OK within struts.
In my situation, I've got UTF-8 of various european languages in the
properties files, but bean:message is still not working for me whereas a
scriplet that forces UTF-8 interpretation will.
Jim
"Bartley, Chris P"
<cbartl03@sprintsp To: "'Struts Users Mailing
List'" <[EMAIL PROTECTED]>
ectrum.com> cc:
Subject: RE: Help with bean:message
encoding problem (UTF-8) anyone?
07/30/2002 09:03
AM
Please respond to
"Struts Users
Mailing List"
I'm pretty unfamiliar with encoding issues, but does Martin's post at the
end of this bug report help you?
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=11267
A shot in the dark,
chris
> -----Original Message-----
> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]
> Sent: Tuesday, July 30, 2002 10:57 AM
> To: Struts Users Mailing List
> Subject: Help with bean:message encoding problem (UTF-8) anyone?
>
>
>
> Hi,
>
> Trying again here with more info:
>
> If I access a property file containing UTF-8 encoded values
> via a scriplet
> in a JSP, the characters come out fine in various browsers.
> Here is the
> scriplet:
>
> <% String testString = MessageResource.getMessage
> ("message.enterZipCode",
> new Locale("DE", "de"));
> testString = new String(testString.getBytes(), "UTF-8");
> %>
> <%=testString%>
>
>
> If I try to render the same property within a strutsified page via
> bean:message, I get garbage where the special characters appear.
>
> I'm pretty ignorant about character encoding schemes, I confess. Am I
> missing something obvious?
>
> I am using tomcat 4.03 and struts 1.01 with jdk 1.3.02 on
> windows machines.
> In both of the above cases, the meta tag in the html
> specifies UTF-8 and
> the http header coming from tomcat to browser specifies UTF-8.
>
> I realize iso is normal with european languages. The reason
> I have UTF-8
> to deal with at this point is that we have quickie
> translations done by
> babelfish engine which outputs UTF-8. In any case, when our
> applications
> begin to move to asian countries, we'll have multiple
> encodings to deal
> with for certain.
>
> Thanks,
>
> Jim
>
>
>
> --
> To unsubscribe, e-mail:
> <mailto:[EMAIL PROTECTED]>
> For additional commands, e-mail:
> <mailto:[EMAIL PROTECTED]>
>
--
To unsubscribe, e-mail: <
mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <
mailto:[EMAIL PROTECTED]>
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
