another thing is regarding multi-language version.i stored all the text in the UI in a constant class.
to switch to another language, simply replace those text with the corresponding in the other language.
however, there is problem with input chinese characters in the text area. (displayed as squares). don't know whether this problem can be solved in JDK1.4. if yes, a chinese version can be developed in minutes.
I can answer some of your doubts:
1) For HTML pages, they CAN be included into the jar file. I did make applications that displays help documents that are included in jar archive.
2) I recommend that you do not use constant class for localization/internationalization. In fact, the Java i18n approach uses the class MessageFormat as well as .properties files that gives a unique name to each constant string/pattern throughout the application.
You can find sample code for the above points from sun's web site. I did both before, so I'm pretty sure they are operational and they are indeed convenient.
2) I recommend that you do not use constant class for localization/internationalization. In fact, the Java i18n approach uses the class MessageFormat as well as .properties files that gives a unique name to each constant string/pattern throughout the application.
You can find sample code for the above points from sun's web site. I did both before, so I'm pretty sure they are operational and they are indeed convenient.