Excellent! We should decide if we want to maintain it or not. Then we can create a package for it.
Stef On May 7, 2010, at 4:17 PM, Hilaire Fernandes wrote: > I have uploaded a new version of the gettext package. I have removed a few > classes used for the itnernal translator. So now, only gettext based catalog > messages is used. > > Philipp, I have added a String>>translateTo: aLocale you can used from > Seaside application. > > If we agree on that protocole, we can have in Pharo-Cire two String messages > defined as follow: > > String>>translated > "answer the receiver translated to the default language" > ^ NaturalLanguageTranslator translate: self > > String>>translatedTo: localeID > "answer the receiver translated to the given locale id" > ^ NaturalLanguageTranslator translate: self toLocale: localeID > > > Then a dummy class NaturalLanguageTranslator withn two class messages: > > NaturalLanguageTranslator class>>translate: aString > ^ aString > > NaturalLanguageTranslator class>>translate: aString toLocale: localeID > ^ aString > > > NaturalLanguageTranslator class is redefined in the Gettext package. > > It should be possible to simplify the whole protocole after removing the > LanguageEditor. This one is totaly unused, and it does not make sense to me > to use Smalltalk to translated string, there are better third party tool to > do that. Can I remove the LanguageEditor? > > Hilaire > > > _______________________________________________ > Pharo-project mailing list > [email protected] > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project _______________________________________________ Pharo-project mailing list [email protected] http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
