JackWang -
The font.properties file typically only maps Java font properties
("MonoSpaced", "SansSerif", etc.) to the actual fonts available on the
client machine. Changing the font.properties file on the server makes no
sense, as the server in a client/server or applet/servlet or whatever
architecture would not be responsible for displaying fonts to the
client.
BUT - font.properties file should only be important if you want to
display fonts for character sets that are not the native encoding of the
operating system under which your JVM is running, for example, if you
want to enable users with an US English operating system to see Japanese
text in your applet (or, say enable Japanese users to be able to see
Simplified Chinese). I am fairly certain that, if your internet user is,
for example, running a Japanese OS with a Japanese version of Netscape
(or whatever client it is that provides the JRE), then everything should
work. The crucial point here should be whether the browser (in a
browser-based application) is localized, so it might not work if the
Japanese user has the English version of Netscape installed (although it
is also possible that the English Netscape installer checks what
operating system locale it is being installed on and then selects the
correct font.properties file to be used, I don't know the answer to
that). And then of course, if you are distributing a JRE yourself with
you app, you can and should take care of these things during
installation.
If you have access to a localized machine, try
http://www.renzop.com/localeviewer.htm - I just put together a quick
test applet for the main Asian languages and Russian - if you see the
strings when you select either one of Japanese, Simplified Chinese,
Traditional Chinese, Korean, or Russian, you should be all set for those
languages. I'll test it out myself from work tomorrow.
Let me know.
Renzo
wx88 wrote:
>
> Renzo,
>
> I have not seen the tutorial and reference of I18N yet,
> but I wish to ask a question first. I know the application
> and the applet in the local machine have no problem in
> dealing with I18n, so long as I change the "font.properties"
> file to add the I18N font.
>
> My question is "font.properties" file is in the machine which
> has JDK/JRE installed, but applet is run with JDK/JRE
> which is in the users machine, not in the server. If my applet
> needs I18N support, need I tell my Internet users to change
> their "font.properties" file in their machine, so as to show
> the I18N codes ? This is not practical. So, the only thing I
> should do is to change the "font.properties" file in the server,
> everything should be OK ?
>
> JackWang
>
> Renzo wrote:
> ... ...
> 4. From what I can tell, the rest is Java I18N as usual. See the I18N
> Tutorial at http://java.sun.com/docs/books/tutorial/i18n/TOC.html. There
> was also a three-part tutorial at http://www.javaworld.com at somepoint.
> Take the first first example of that tutorial and add Japanese to the
> choices ("ja", "JP") to allow you to test whether you have correctly
> installed the font.properties file. If you did, you'll see Japanese
> characters when you select Japanese in this applet (in appletviewer or
> in the browser).
>
> Hope this helps.
> Renzo
----------------------------------------------------------------------
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
