Re: Doubt in I18N

2001-06-14 Thread Craig R. McClanahan 



On Thu, 14 Jun 2001, Sunil P.S. wrote:

 Is there anything extra to be done for application to work in other
 languages. The docs says that it is same as JDK internationalization
 and we have to just modify the web.xml and pass the properties file as
 init paramter to the ActionServlet. 
 
 Is there anything extra to be done in the code
 

If you are using bean:message to display internationalized messages (or
the appropriate calls to the application's MessageResources object in your
Actions), you don't have to make any code changes to work in multiple
languages -- just add your properties files for the messages in each
appropriate language.  This works well as long as all of the languages can
be displayed in the same character encoding -- if you need different
encodings for different languages, you may need to organize your app
differently.

 
 -sunil.
 

Craig McClanahan

Re: Doubt in I18N

2001-06-13 Thread Jonathan Asbell 





  - Original Message - 
  From: 
  Greg 
  Murray 
  To: [EMAIL PROTECTED] 
  Sent: Tuesday, May 01, 2001 1:49 PM
  Subject: Re: Can not read i18n properties 
  file
  Hi all, 
  Ihave encountered this behavior in the past .properties files must be 
  converted to ascii using the java sdk native to ascii before the display. 
  Once converted your characters should be viewable. Also remember to set the 
  Content-Type as specified. 
  gm/  
  Jason Chaffee wrote: 
   
That would be my guess as well. Take a look at the 
html source that is being produced and see if there is a charset header, if 
there isn't copy the source to a static file and add a charset header and 
try to load it in IE, this should give you your answer. 
-Original Message- From: 
shunhui zhu [mailto:[EMAIL PROTECTED]] 
Sent: Tuesday, May 01, 2001 11:18 AM To: [EMAIL PROTECTED] Subject: 
Re: Can not read i18n properties file 
Pau, I did a similar test for a chinese version with 
resource_zh.properties. If I change my browser 
language preferences (in IE), I do get the chinese 
version, although to display it correctly, I needed 
to select chinese encoding in IE's view menu. My 
guess is that the response header is not setting 
the "Content-language" header or the charset 
header, but I haven't looked into it. 
Shunhui --- Sean Pau 
[EMAIL PROTECTED] wrote:  I test 
creating resource properties file for  Japanese 
language. I use  Windows Notepad and edit 
resources_ja.properties and  save it under 
UTF-8 and  Unicode format. Struts could display 
when the file  is in UTF-8 format but 
 the text came out rubbish. When the file is in 
 Unicode format, Struts is not  reading it, instead it reads the default  resources.properties file. Both  
UTF-8 and Unicode format resources_ja.properties  files display the Japanese  text 
OK when I drag it into IE and also WordPad. Pls  help. Thanks_ 
 Do You Yahoo!?  Get your 
free @yahoo.com address at  http://mail.yahoo.com 
 
__ 
Do You Yahoo!? Yahoo! Auctions - 
buy the things you want at great prices http://auctions.yahoo.com/