• Post Reply Bookmark Topic Watch Topic
  • New Topic
programming forums Java Mobile Certification Databases Caching Books Engineering Micro Controllers OS Languages Paradigms IDEs Build Tools Frameworks Application Servers Open Source This Site Careers Other Pie Elite all forums
this forum made possible by our volunteer staff, including ...
Marshals:
  • Campbell Ritchie
  • Jeanne Boyarsky
  • Ron McLeod
  • Paul Clapham
  • Liutauras Vilda
Sheriffs:
  • paul wheaton
  • Rob Spoor
  • Devaka Cooray
Saloon Keepers:
  • Stephan van Hulst
  • Tim Holloway
  • Carey Brown
  • Frits Walraven
  • Tim Moores
Bartenders:
  • Mikalai Zaikin

japanese language properties files don't work, all others do

 
Ranch Hand
Posts: 109
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
I am working on a Struts 1.0 application that needs to have a Japanese interface. Adding a .ja properties file does not work even though the locale is being set correctly. It appears that Struts just does not pick up the file.

Can anyone offer some guidance on this problem? I've been told this is a problem only with Struts 1.0 but this project does not have the budget to port to a newer version of Struts so I need some sort of work around.

Thanks,
--beeky
 
William Stafford
Ranch Hand
Posts: 109
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
I found the problem and solution so I'm posting it as a reply to my own post in case the original post turns up on a search.

I owe a big apology to Struts, the problem had nothing to do with Struts. As far as I can tell Struts 1.0 has no problems with Japanese properties.

The problem turned out to be the properties file itself. The properties file was created using MSWord and the encoding that resulted was not the same as used by the rest of the application. When a tag asked for a message using a particular key, that key matched in all properties files but the Japanese file. I'm guessing that the bit pattern used to hash the messages was different for the Japanese file so nothing in the Japanese file ever matched the keys in the application.

The solution was to recreate the properties file using the NativeToAscii tool. I would think any re-encoding would have solved the problem.
 
With a little knowledge, a cast iron skillet is non-stick and lasts a lifetime.
reply
    Bookmark Topic Watch Topic
  • New Topic