Re:Extended localization - multiple applications

Hi James,

we run in the past into the same problem to find a easier way for  
localizing a application.
Keeping up the Localizable.strings file up to date is not really a  
nice job. In our case we had
over 900 keys and four languages.

We decided to create a Localizer Framework which is own eomodel and  
database.
There is a LocalizedKey class holding the key and the for each  
language a field for the localized text.
This could be also make more dynamically if you do that in your own  
eo. But for our needs this was the best solution.

The we wrote some components to add and edit keys in a backoffice  
manner. Also we implemented a reduced editor
view, where Localization Service People can directly log in and edit  
the stuff.

To not reinvent the wheel we extend  the ERXLocalizer class from  
Project Wonder.
It was something to do, but now we have the possiblity to localize  
every application very easy by adding the framework to the project,
defining some properties (url for database, password for edit) and  
its working.

Best,

André

Am 10.04.2006 um 21:00 schrieb [email protected]:


> Date: Mon, 10 Apr 2006 14:57:11 +0200
> From: "Brook, James" <[email protected]>
> Subject: Extended localization - multiple applications
> To: [email protected]
> Message-ID:
> 	<1FDCE9F824991441A7CE1CFBB0CED3740534BE1A@nlcbbms02.media.ds.upc.biz>
> Content-Type: text/plain
>
> My organization uses WebObjects as its primary means for developing  
> and
> deploying dynamic Web applications. These applications are  
> eventually likely
> to be deployed across more than 10 European countries. At the  
> moment, each
> application contains a 'Localizable.strings' plist for each  
> language that it
> supports.
>
> We are already running into problems with this approach. We will  
> have a
> requirement to share localized strings across multiple  
> applications. We will
> have another requirement for non technical Web producers to be able to
> change the localizations in their own territory.
>
> To meet these requirements I envisage some sort of localization  
> database and
> an editorial interface for producers to use. It might also be very  
> useful to
> be able to provide the producers with some context as to where the  
> strings
> get used, so that they understand the consequences of changes that  
> they
> make.
>
> I am writing to the list to ask if anyone is willing to share any  
> experience
> with tackling this sort of problem and what might be the best  
> approach to
> take. I am getting very tired of receiving broken plist files, with  
> badly
> encoded two byte characters via e-mail and then having to make new  
> releases
> of the applications to deploy them!
>
> --
> James
>
>
> ------------------------------
>
> _______________________________________________
> WebObjects-dev mailing list
> [email protected]
> http://www.omnigroup.com/mailman/listinfo/webobjects-dev
>
>
> End of WebObjects-dev Digest, Vol 11, Issue 10
> **********************************************

André Koppany			Bertholdstr.	21
mackoy consulting		80809 München
[email protected]		Tel. +49/(0)89/3402 - 90 66

_______________________________________________
WebObjects-dev mailing list
[email protected]
http://www.omnigroup.com/mailman/listinfo/webobjects-dev