Re: Localization
Re: Localization
- Subject: Re: Localization
- From: Yvan KOENIG <email@hidden>
- Date: Sun, 11 Sep 2005 15:40:50 +0200
Le 11 sept. 2005 , à 12:33, kai a écrit :
On 11 Sep 2005, at 09:08, jean-louis valero wrote:
I'm writing in France an AppleScript application which must be used
in USA. The target app is RealPlayer.
When I open its library (in Paris), most of the language is in french.
For example, "lecture" is used instead of "play", "fenêtre" instead
of "window"
As I thought that the dialect automatically changes to match the
operating system being used on any given Macintosh, I made my little
app in french... and sent it over the Ocean. My friend said he
received message like this:
"the variable lecture is not defined" etc...
What is wrong? I can't imagine my friend obliged to use a French
RealPlayer version...
How can I make an universal version ?
How did you save your script, Jean-Louis?
If you saved it as 'text', try saving it as 'script'. That way, any
application-specific terms should be saved as raw code which,
hopefully, should translate appropriately for your friend...
Hello kai
the problem is that interface objects are localised.
For menu and menu item names, one may use index in lieu of names but
jean-louis told me that some other objects are also localised.
I'm afraid that the way to get rid of that would be a code of this kind:
set vLoc to [localisation ID]
if vLoc is french then
set obj1 to "position du clip"
set obj2 to "xxx_FR"
else if vLoc is english then
set obj1 to "clip position"
set obj2 to "xxx_EN"
else if vLoc is italian then
…
end if
after that, use variables in lieu of the object names.
Yvan KOENIG
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Applescript-users mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden