internationalization
Locked
 
|
From the pier list... On May 6, 2009, at 2:26 AM, Lukas Renggli wrote: >> Ok, after said that, I want to add int18 to my website but I don't >> want to >> touch Pier code. So, the solution I thought is this: > > That would be a goal for the next big release then. I created an > issue: <http://code.google.com/p/pier/issues/detail?id=95>. > > We were sort of thinking of providing an internationalization package > as part of Seaside 2.9, because this is something quite a lot of > people want. Especially in the context of web applications. However we > didn't do anything yet. At some point in the not so close yet not so distant future of the application we are porting over to seaside, we are going to have to internationalize it ( existing application currently has translation for english, spanish, french & german + localization etc ). I'd rather not be coming up with a solution when one is already being worked on. Is this something that is going to happen in the not so distant future? If yes, how can we contribute. If no, we'll move ahead with a solution that works for our specific scenario and perhaps it works for others. Something that is part of Seaside itself and won't be broken by future updates is obviously the ideal. _______________________________________________ seaside mailing list [hidden email] http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside |
Re: internationalization
|
|
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. _______________________________________________ seaside mailing list [hidden email] http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside |
|
|
In reply to this post by SeanTAllen
GemStone has a LanguageDictionary, but I would query the GemStone Customer Forum[1] to see if there are different alternatives.
Dale [1] http://earth.lyris.net/cgi-bin/lyris.pl?enter=gemstone-smalltalk ----- "Sean Allen" <[hidden email]> wrote: | From the pier list... | | On May 6, 2009, at 2:26 AM, Lukas Renggli wrote: | | >> Ok, after said that, I want to add int18 to my website but I don't | | >> want to | >> touch Pier code. So, the solution I thought is this: | > | > That would be a goal for the next big release then. I created an | > issue: <http://code.google.com/p/pier/issues/detail?id=95>. | > | > We were sort of thinking of providing an internationalization | package | > as part of Seaside 2.9, because this is something quite a lot of | > people want. Especially in the context of web applications. However | we | > didn't do anything yet. | | At some point in the not so close yet not so distant future of the | application | we are porting over to seaside, we are going to have to | internationalize it | ( existing application currently has translation for english, spanish, | | french & | german + localization etc ). | | I'd rather not be coming up with a solution when one is already being | | worked on. | Is this something that is going to happen in the not so distant | future? If yes, | how can we contribute. | | If no, we'll move ahead with a solution that works for our specific | scenario | and perhaps it works for others. | | Something that is part of Seaside itself and won't be broken by future | | updates | is obviously the ideal. | _______________________________________________ | seaside mailing list | [hidden email] | http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside _______________________________________________ seaside mailing list [hidden email] http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside |
|
|
In reply to this post by SeanTAllen
2009/5/23 Sean Allen <[hidden email]>:
> > From the pier list... > > On May 6, 2009, at 2:26 AM, Lukas Renggli wrote: > >>> Ok, after said that, I want to add int18 to my website but I don't want >>> to >>> touch Pier code. So, the solution I thought is this: >> >> That would be a goal for the next big release then. I created an >> issue: <http://code.google.com/p/pier/issues/detail?id=95>. >> >> We were sort of thinking of providing an internationalization package >> as part of Seaside 2.9, because this is something quite a lot of >> people want. Especially in the context of web applications. However we >> didn't do anything yet. > > At some point in the not so close yet not so distant future of the > application > we are porting over to seaside, we are going to have to internationalize it > ( existing application currently has translation for english, spanish, > french & > german + localization etc ). > > I'd rather not be coming up with a solution when one is already being worked > on. > Is this something that is going to happen in the not so distant future? If > yes, > how can we contribute. > > If no, we'll move ahead with a solution that works for our specific scenario > and perhaps it works for others. > > Something that is part of Seaside itself and won't be broken by future > updates > is obviously the ideal. I trying to convince people to rip gettext out of OLPC. The big advantage would be all the existing third part tools that support it and the Smalltalk side would be fairly simple. It would require a bit of customization (mostly deletes and renames) to comply with "Seaside standards" that that part should also be fairly easy. Cheers Philippe _______________________________________________ seaside mailing list [hidden email] http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside |
| Free forum by Nabble | Edit this page |