> The ~600 method changeset which converts the UI to use translated  
> strings will be incorporated soon... probably tomorrow (Saturday)  
> evening.  It sounds like the "explicit" approach has been more or less  
> agreed upon by the people who have an interest in translation issues.  
> (see Stef's message below)  It's been approved by Stephane (and  
> others), although I guess it never was published as an [enh], perhaps  
> because it was too large.

Yes it bounced several times so I stopped sending it.
>
> Anyway, this is a bit of a warning before the changeset goes in, in  
> case anyone has a comment.
>
> I guess this does mean that people adding text to the end-user UI will  
> need to remember to add #translated messages to the strings that  
> appear in the UI.  (The end-user UI appears to include etoys, morphs,  
> filelists, etc. but not development tools like browsers.)  Anyway,  
> this adds a minor bit of complexity, but having Squeak easily  
> available in many languages will be a great thing!
>
> The changeset is currently here:
>
> http://swiki.agro.uba.ar/small_land/uploads/191/ 
> CompleteTranslationFor37-dgd.cs.gz
>
> There are a few conflicts with more recent methods since this  
> changeset was written, but those should be covered by Stephane's  
> BabelConflicts fix from yesterday, which I'll also include as an  
> update.

Hi doug

Diego will issue soon the rest of the conflicts in a separate cs  
(around 5) so that we have everything. So go ahead this will be fixed  
easily because the conflicts are  normally straighforward.


>
> - Doug
>
>
> -------- Original Message --------
> Subject: 	About babel
> Date: 	Sat, 8 Nov 2003 21:57:32 +0100
> From: 	ducasse <ducasse at iam.unibe.ch>
> Reply-To: 	The general-purpose Squeak developers list  
> <squeak-dev at lists.squeakfoundation.org>
> To: 	The list <squeak-dev at lists.squeakfoundation.org>
>
>
>
> Hi
>
> during the squeak party here we (markus, marcus, lukas, hans, diego,
> alex and me) got a good discussion on how to proceed with the two babel
> options andreas approach with literal changes and translated of diego.
>
> After a lot of interesting discussions we arrive to a consensus that
> diego approach is better because
> it makes things explicit and that this is already done and ready to go
> in the image.
>
> So I'm planning to wait until doug includes in the stream the pending
> approved items to check conflicts with the huge changeset diego
> produced: 600 methods. For now there are 15 conflicts simple one I
> guess with 3.7a and with that we will have a fully language aware basic
> image. Just waiting for translators to proceed.
>
>
> Stef
>
>
>