[Seaside] Multi-lingual/Multi-locale applications

[Sean Allen]

I'd be interested in learning how they deal with the situation.

If we go the seaside route, we will be using gemstone but the more  
knowledge
I have, the better.

On May 23, 2008, at 12:39 PM, Boris Popov wrote:

> Sean,
>
> VisualWorks version of Seaside supports per-session locales and  
> message
> catalogs dealing with both formatting and language issues AFAIK. I was
> going to look at that closer in a week or two and could report back if
> you're interested.
>
> -Boris
>
> -- 
> +1.604.689.0322
> DeepCove Labs Ltd.
> 4th floor 595 Howe Street
> Vancouver, Canada V6C 2T5
> http://tinyurl.com/r7uw4
>
> boris at deepcovelabs.com
>
> CONFIDENTIALITY NOTICE
>
> This email is intended only for the persons named in the message
> header. Unless otherwise indicated, it contains information that is
> private and confidential. If you have received it in error, please
> notify the sender and delete the entire message including any
> attachments.
>
> Thank you.
>
>> -----Original Message-----
>> From: seaside-bounces at lists.squeakfoundation.org [mailto:seaside-
>> bounces at lists.squeakfoundation.org] On Behalf Of Sean Allen
>> Sent: Friday, May 23, 2008 9:32 AM
>> To: Seaside - general discussion
>> Subject: [Seaside] Multi-lingual/Multi-locale applications
>>
>> 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