On Mon, May 19, 2014 at 6:10 PM, Marcus Denker <marcus.denker@inria.fr> wrote:

On 19 May 2014, at 18:03, Hilaire Fernandes <hilaire.fernandes@gmail.com> wrote:

> It will ease a lot of things but is it really the right things to do?

1) Pharo itself should be multi-lingual eventually
2) now we have code in the image that seemingly nobody should
use. Why is it there? Does that make sense?

I am not sure if there is any useful description about the System-Localization package somewhere because when I started to look for multi-lingual functionality in Pharo, I was told to look at GetText. And then I found some very useful text explaining how to use it��
(http://pharo.gemtalksystems.com/book/LanguageAndLibraries/Localisation/PreparingImage/).��

But it is essential to merge the classes from System-Localization package and into GetText. I had a look at System-Localization package. Its Locale class provides services for language management inside the image. I use these services it in my application to switch the language of the image. ISOLanguageDefinition class, though currently not used, provides implementation for ISO standard.

My suggestion:
- not to throw away pharo package
- merge pharo package with GetText and name the merged package as system-localization in Pharo (for default multi-lingual functionality inside the image).
- write some tests (because currently there are none).

What do you say?

regards,
Usman




��

> (i.e. all the new packages carved in Pharo now)
>
> Hilaire
>
> Le 19/05/2014 17:52, Marcus Denker a ��crit :
>> Maybe we should have the get text solution in the image by default?
>
> --
> Dr. Geo http://drgeo.eu
>
>