[Seaside] Multi-lingual/Multi-locale applications

[James Robertson]

As an FYI, Cincom Smalltalk (using Seaside or anything else) supports  
multiple locales per image.  It's discriminated at the process level,  
so a given application can serve different locales out if desired.  As  
Philippe says below, you would need the latest 7.6.  You can download  
that here:

http://www.cincomsmalltalk.com/userblogs/cincom/blogView?content=smalltalk

To try it out


James Robertson
Cincom Smalltalk Product Evangelist
http://www.cincomsmalltalk.com/blog/blogView
Talk Small and Carry a Big Class Library




On May 25, 2008, at 3:36 AM, Philippe Marschall wrote:

> You're a bit out of luck then.
>
> Both Squeak and GemStone support only one locale per image. This is
> most certainly not what you want for a web application.
>
> Regarding various locale items like number formatting, currency symbol
> that should be supported on Gemstone but not Squeak. If you look a
> Squeak's locale class, it has all the necessary functionality but it
> is not implemented. I think this is fixed in none of the Squeak forks.
> The OLPC Squeak fork supports gettext but you'd have to rip that out
> and port it yourself. Else you'll have to build you own translation
> system.
>
> You might want to ask on glass-beta for more concrete information
> about the situation on GemStone.
>
> Afaik only the latest VW 7.6 should do what you need, I don't know
> about GST and Dolphin though.
>
> Cheers
> Philippe
>
> 2008/5/24 Sean Allen <sean at monkeysnatchbanana.com>:
>> It would end up being Gemstone for final positioning.
>>
>> Being able to play around with in Squeak initially would be nice.
>>
>> On May 24, 2008, at 3:15 AM, Philippe Marschall wrote:
>>
>>> Which dialect, Squeak, VW, Gemstone, Dolphin?
>>>
>>> Cheers
>>> Philippe
>>>
>>>
>>> 2008/5/23 Sean Allen <sean at monkeysnatchbanana.com>:
>>>>
>>>> Looking for advice on best way to handle following situation:
>>>>
>>>> same application running with different database on different  
>>>> images on
>>>> different machines
>>>> where application code is the same but some key configurations are
>>>> different
>>>>
>>>> such as various locale items like number formatting, currency  
>>>> symbol and
>>>> large scale text changes
>>>> do to different languages being used.
>>>>
>>>> i have very limited seaside and smalltalk experience right now,  
>>>> just from
>>>> playing around with stuff,
>>>> but the project we are considering moving over would need to  
>>>> tackle these
>>>> issues immediately.
>>>>
>>>> multiple routes to obtain what we need appreciated.
>>>>
>>>> our current code base ( in python ) uses a combination of  
>>>> translated
>>>> templates, get text and small
>>>> conf files to handle what is needed. while not ideal, it works  
>>>> and easy
>>>> to
>>>> manage.
>>>>
>>>> 99% of the work is handled by having the different templates,  
>>>> obviously,
>>>> moving to programmatic html
>>>> eliminates the ease there ( but gets rid of a maintenance  
>>>> headache of
>>>> redoing the same html
>>>> across multiple templates ).
>>>> _______________________________________________
>>>> seaside mailing list
>>>> seaside at lists.squeakfoundation.org
>>>> http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside
>>>>
>>> _______________________________________________
>>> seaside mailing list
>>> seaside at lists.squeakfoundation.org
>>> http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside
>>
>> _______________________________________________
>> seaside mailing list
>> seaside at lists.squeakfoundation.org
>> http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside
>>
> _______________________________________________
> seaside mailing list
> seaside at lists.squeakfoundation.org
> http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside
>