Preparing Pharo-Core for i18n framework

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
4 messages Options
Reply | Threaded
Open this post in threaded view
|

Preparing Pharo-Core for i18n framework

hilaire
CONTENTS DELETED
The author has deleted this message.
Reply | Threaded
Open this post in threaded view
|

Re: Preparing Pharo-Core for i18n framework

hilaire
CONTENTS DELETED
The author has deleted this message.
Reply | Threaded
Open this post in threaded view
|

Re: Preparing Pharo-Core for i18n framework

Stéphane Ducasse
Ok can you open bug entry ticket
else we cannot follow


On May 13, 2010, at 12:11 PM, Hilaire Fernandes wrote:

> Also I suggest to remove the LanguageEditor from the image.
>
> Hilaire
>
> Hilaire Fernandes a écrit :
>> To be compatible with the gettext package I have pushed in Inbox Collection-Strings and System-Localization changes.
>> After the changes, NaturalLanguageTranslator becomes in core a dummy class responding to two dummy messages. This dummy class is later replaced by the real one when the developer loads the gettext package
>> String>>translate reflect this change.
>> I really don't know how to load these two package in Pharo without breaking the image. The only possibility I see is to first hand edit String>>translated to respond self, then load System-Localisation and Collection-String from Inbox.
>> Tiny hand edit.
>> We should get this tiny changes in as the Seaside people seems to need it as well.
>> Hilaire
>
>
> _______________________________________________
> Pharo-project mailing list
> [hidden email]
> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project


_______________________________________________
Pharo-project mailing list
[hidden email]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
Reply | Threaded
Open this post in threaded view
|

Re: Preparing Pharo-Core for i18n framework

Stéphane Ducasse
In reply to this post by hilaire
ok I will have a look now.

Stef

On May 13, 2010, at 12:00 PM, Hilaire Fernandes wrote:

> To be compatible with the gettext package I have pushed in Inbox Collection-Strings and System-Localization changes.
>
> After the changes, NaturalLanguageTranslator becomes in core a dummy class responding to two dummy messages. This dummy class is later replaced by the real one when the developer loads the gettext package
>
> String>>translate reflect this change.
>
> I really don't know how to load these two package in Pharo without breaking the image. The only possibility I see is to first hand edit String>>translated to respond self, then load System-Localisation and Collection-String from Inbox.
>
> Tiny hand edit.
>
> We should get this tiny changes in as the Seaside people seems to need it as well.
>
> Hilaire
>
>
> _______________________________________________
> Pharo-project mailing list
> [hidden email]
> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project


_______________________________________________
Pharo-project mailing list
[hidden email]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project