W3C home > Mailing lists > Public > www-international@w3.org > July to September 2005

RE: Internationalizing JavaScript's confirm() method

From: souravm <SOURAVM@infosys.com>
Date: Mon, 5 Sep 2005 10:46:39 +0530
Message-ID: <56E2573C375A414191118970BDE06A1519529DEA@kecmsg06.ad.infosys.com>
To: "Jon Hanna" <jon@hackcraft.net>, <www-international@w3.org>


Hi Jin,

Actually I got some info how to do it (some work around)

Option 1 :
var theURL = "some.jsp?";
var someFeatures =
'dialogHeight:250px;dialogLeft:115;dialogTop:115;dialogWidth:475px;resiz
able:yes;';
var argsOut = window.showModalDialog(theURL, "", someFeatures);

Instead of 'some.jsp' we create dynamic html with message to be
displayed and pass it. It is working.

Option 2 :
Using CPropertySheet class - as Arfen form this group replied. I've to
test yet it.

Now coming to your comment "That seems to be the way it should be
really" - I personally don't think this is the way it should be as,
according to me, does not take care of some usage scenarios (I've
described below).

Let us consider a scenario where a user from Japan, Me. XYZ san, has an
account in a MNC bank in its local branch in Japan. The bank provides
the required feature in its web based account access system so that Mr.
XYZ san can access his accounts in Japanese language. Now let us assume
Mr. XYZ san, is a big executive traveling around the world frequently
and sometimes he has to access his accounts from browser running on a
machine in US (and surely in that machine the locale is US English and
for all practical purpose it would not be possible for him to change the
locale to Japanese). So in this case the application will be all in
Japanese except these javascripts confirm messages - which is surely not
very nice from the user experience perspective.

And this is not a hypothetical situation I'm describing out here. This
was one of my client's requirements while I was planning for the
architecture for internationalization of their already existing
application.

In general I am not for any local machine's setting based behaviors (in
case of internationalization) which cannot be controlled from Server
application. Local machine's setting should be used as a fallback
mechanism not as the standard behavious.

Any takers for this opinion ?

Regards,
Sourav




-----Original Message-----
From: www-international-request@w3.org
[mailto:www-international-request@w3.org] On Behalf Of Jon Hanna
Sent: Friday, September 02, 2005 8:47 PM
To: www-international@w3.org
Subject: Re: Internationalizing JavaScript's confirm() method


souravm wrote:
> Is there any way to control the language of the "Yes" and "no" buttons
> displayed by JavaScript's confirm() method from the server application
?

I'm pretty sure there isn't.

> The language in which those buttons are displayed is governed by the
> locale of the machine on which the browser is running.

That seems to be the way it should be really.


**************** CAUTION - Disclaimer *****************
This e-mail contains PRIVILEGED AND CONFIDENTIAL INFORMATION intended solely for the use of the addressee(s). If you are not the intended recipient, please notify the sender by e-mail and delete the original message. Further, you are not to copy, disclose, or distribute this e-mail or its contents to any other person and any such actions are unlawful. This e-mail may contain viruses. Infosys has taken every reasonable precaution to minimize this risk, but is not liable for any damage you may sustain as a result of any virus in this e-mail. You should carry out your own virus checks before opening the e-mail or attachment. Infosys reserves the right to monitor and review the content of all messages sent to or from this e-mail address. Messages sent to or from this e-mail address may be stored on the Infosys e-mail system.
***INFOSYS******** End of Disclaimer ********INFOSYS***
Received on Monday, 5 September 2005 05:19:11 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 2 June 2009 19:17:05 GMT