Home/ Questions/Q 53009
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-10T16:59:47+00:00

I’m experimenting with internationalization by making a Hello World program that uses properties files

  • 0

I’m experimenting with internationalization by making a Hello World program that uses properties files + ResourceBundle to get different strings.

Specifically, I have a file ‘messages_en_US.properties’ that stores ‘hello.world=Hello World!’, which works fine of course.

I then have a file ‘messages_ja_JP.properties’ which I’ve tried all sorts of things with, but it always appears as some type of garbled string when printed to the console or in Swing. The problem is obviously with the reading of the content into a Java string, as a Java string in Japanese typed directly into the source can print fine.

Things I’ve tried:

  • The .properties file in UTF-8 encoding with the Japanese string as-is for the value. Something I read indicates that Java expects a properties file to be in the native encoding of the system…? It didn’t work either way.
  • The file in default encoding (ISO-8859-1) and the value stored as escaped Unicode created by the native2ascii program included with Java. Tried with a source file in various Japanese encodings… SHIFT-JIS, EUC-JP, ISO-2022-JP.

Edit:

I actually figured this out while I was typing this, but I figured I’d post it anyway and answer it in case it helps anyone.

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. I realized that native2ascii was assuming (surprise) that it was converting from my operating system’s default encoding each time, and as such not producing the correct escaped Unicode string.

    Running native2ascii with the ‘-encoding encoding_name‘ option where encoding_name was the name of the source file’s encoding (SHIFT-JIS in this case) produced the correct result and everything works fine.

    Ant also has a native2ascii task that runs native2ascii on a set of input files and sends output files wherever you want, so I was able to add a builder that does that in Eclipse so that my source folder has the strings in their original encoding for easy editing and building automatically puts converted files of the same name in the output folder.

    • 0