Localisation of Applescript strings

Hi,

Eric Bachard sent me the following link, which is some
patches for  
fondu and localisation.

http://eric.bachard.free.fr/mac/fondu/old_patch%20/i57
252- 
updatefondu.patch.txt

I have taken a quick look, and they cannot simply be applied
since a  
lot of the code has been integrated already and in some
cases been  
updated again.

First off trying to ignore the code that has been updated is
 
important. Then deciding on the best localisation form is
the next step.

It would appear that the key line that doesn't work in
Panther, but  
does work in Tiger is:
+		return localized string aKey from table
"Localizable"
Please correct me if I'm wrong with my assertion.

I also need some more information on the way that ooo deals
with the  
localisation of strings. It appears that a file
desktop/macosx/source/ 
messages.ulf is being used. Does this comply with the
standard  
localisation mechanisms for ooo? Is this the way that
strings are  
added to ooo?

I will look into this further as time permits.

Shaun

	
	
		
___________________________________________________________

All new Yahoo! Mail "The new Interface is stunning in
its simplicity and ease of use." - PC Magazine 
http://uk.doc
s.yahoo.com/nowyoucan.html

------------------------------------------------------------
---------
To unsubscribe, e-mail: mac-unsubscribeporting.openoffice.org
For additional commands, e-mail: mac-helpporting.openoffice.org

Hi Shaun,

All the related code and also description of the
OOo-integrated localization
process is in issue 57252 (look especially at comments by
obr and ssa).

We already had 100% working solution for Tiger, but it was
dropped, because
the Panther implementation would have been completely
different.

Indeed, only Tiger and later support:
    'return localized string aKey from table
"Localizable" '

If the cws macosxversioning01 is ever going to get
integrated, then there
will be files moved around in desktop/macosx/source/.

Localization stuff might have some conflicts with that.

The approach used with the applescript localisation could
also be extended
to any custom MacOSX native strings, such as .pkg installer
or others.

            Mox

On 2/6/07, Shaun McDonald <mcdonaldshaunyahoo.co.uk> wrote:
>
> Hi,
>
> Eric Bachard sent me the following link, which is some
patches for
> fondu and localisation.
>
> http://eric.bachard.free.fr/mac/fondu/old_patch%20/i57
252-
> updatefondu.patch.txt
>
> I have taken a quick look, and they cannot simply be
applied since a
> lot of the code has been integrated already and in some
cases been
> updated again.
>
> First off trying to ignore the code that has been
updated is
> important. Then deciding on the best localisation form
is the next step.
>
> It would appear that the key line that doesn't work in
Panther, but
> does work in Tiger is:
> +               return localized string aKey from table
"Localizable"
> Please correct me if I'm wrong with my assertion.
>
> I also need some more information on the way that ooo
deals with the
> localisation of strings. It appears that a file
desktop/macosx/source/
> messages.ulf is being used. Does this comply with the
standard
> localisation mechanisms for ooo? Is this the way that
strings are
> added to ooo?
>
> I will look into this further as time permits.
>
> Shaun
>
>
>
>
>
___________________________________________________________
> All new Yahoo! Mail "The new Interface is stunning
in its simplicity and
> ease of use." - PC Magazine
> http://uk.doc
s.yahoo.com/nowyoucan.html
>
>
------------------------------------------------------------
---------
> To unsubscribe, e-mail: mac-unsubscribeporting.openoffice.org
> For additional commands, e-mail: mac-helpporting.openoffice.org
>
>


-- 
Mox on G