<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=utf-8">
<META NAME="Generator" CONTENT="MS Exchange Server version 6.5.7654.12">
<TITLE>Re: [Seaside] internationalization</TITLE>
</HEAD>
<BODY>
<!-- Converted from text/plain format -->
<P><FONT SIZE=2>We've been using visualworks catalogs for a while now to translate the app and it worked well. I had to hack it to fix loading of multiple languages in the same image, but I imagine it is fixed for upcoming 7.7 release, other than that it works as advertised.<BR>
<BR>
-Boris (via BlackBerry)<BR>
<BR>
----- Original Message -----<BR>
From: seaside-bounces@lists.squeakfoundation.org <seaside-bounces@lists.squeakfoundation.org><BR>
To: Seaside - general discussion <seaside@lists.squeakfoundation.org><BR>
Sent: Sat May 23 06:11:16 2009<BR>
Subject: [Seaside] internationalization<BR>
<BR>
<BR>
From the pier list...<BR>
<BR>
On May 6, 2009, at 2:26 AM, Lukas Renggli wrote:<BR>
<BR>
>> Ok, after said that, I want to add int18 to my website but I don't <BR>
>> want to<BR>
>> touch Pier code. So, the solution I thought is this:<BR>
><BR>
> That would be a goal for the next big release then. I created an<BR>
> issue: <<A HREF="http://code.google.com/p/pier/issues/detail?id=95">http://code.google.com/p/pier/issues/detail?id=95</A>>.<BR>
><BR>
> We were sort of thinking of providing an internationalization package<BR>
> as part of Seaside 2.9, because this is something quite a lot of<BR>
> people want. Especially in the context of web applications. However we<BR>
> didn't do anything yet.<BR>
<BR>
At some point in the not so close yet not so distant future of the <BR>
application<BR>
we are porting over to seaside, we are going to have to <BR>
internationalize it<BR>
( existing application currently has translation for english, spanish, <BR>
french &<BR>
german + localization etc ).<BR>
<BR>
I'd rather not be coming up with a solution when one is already being <BR>
worked on.<BR>
Is this something that is going to happen in the not so distant <BR>
future? If yes,<BR>
how can we contribute.<BR>
<BR>
If no, we'll move ahead with a solution that works for our specific <BR>
scenario<BR>
and perhaps it works for others.<BR>
<BR>
Something that is part of Seaside itself and won't be broken by future <BR>
updates<BR>
is obviously the ideal.<BR>
_______________________________________________<BR>
seaside mailing list<BR>
seaside@lists.squeakfoundation.org<BR>
<A HREF="http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside">http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside</A><BR>
</FONT>
</P>
</BODY>
</HTML>