Hi, When GetText package (http://smalltalkhub.com/#!/~PharoExtras/Gettext) is loaded in Pharo, it overwrites two Pharo classes with its own in System-Localization package: LocalID and NaturalLangaugeTranslator. Although so far I haven't seen any bugs in GetText because of this anomaly, one of the side-effects is that we get a dirty package in Monticello browser. Does anyone who is knowledge about the history of two packages know the reason to create classes with identical names? A solution would be to rename these classes in one of the packages. I have know a bit about the internals of GetText so I would be biased towards renaming its but I would need your suggestions/confirmation on how to proceed/which one to modify. tx. usman
usman I have no idea On 19/5/14 12:25, Usman Bhatti wrote:
Hi,
When GetText package (http://smalltalkhub.com/#!/~PharoExtras/Gettext <http://smalltalkhub.com/#%21/%7EPharoExtras/Gettext>) is loaded in Pharo, it overwrites two Pharo classes
what do you mean by overrides?
with its own in System-Localization package: LocalID and NaturalLangaugeTranslator. Although so far I haven't seen any bugs in GetText because of this anomaly, one of the side-effects is that we get a dirty package in Monticello browser.
Does anyone who is knowledge about the history of two packages know the reason to create classes with identical names?
A solution would be to rename these classes in one of the packages. I have know a bit about the internals of GetText so I would be biased towards renaming its but I would need your suggestions/confirmation on how to proceed/which one to modify. It would be good to understand the two because may be we could build a better package.
Stef
tx.
usman
On Mon, May 19, 2014 at 2:27 PM, stepharo <stepharo@free.fr> wrote:
usman
I have no idea
On 19/5/14 12:25, Usman Bhatti wrote:
Hi,
When GetText package (http://smalltalkhub.com/#!/~PharoExtras/Gettext < http://smalltalkhub.com/#%21/%7EPharoExtras/Gettext>) is loaded in Pharo, it overwrites two Pharo classes
what do you mean by overrides?
GetText removes these two already existing classes to write of its own with the same name.
with its own in System-Localization package: LocalID and
NaturalLangaugeTranslator. Although so far I haven't seen any bugs in GetText because of this anomaly, one of the side-effects is that we get a dirty package in Monticello browser.
Does anyone who is knowledge about the history of two packages know the reason to create classes with identical names?
A solution would be to rename these classes in one of the packages. I have know a bit about the internals of GetText so I would be biased towards renaming its but I would need your suggestions/confirmation on how to proceed/which one to modify.
It would be good to understand the two because may be we could build a better package.
I only know GetText that's why I was asking for help with System-Localization. So, I'll need some feedback from the people who know about these packages before starting any modifications.
Stef
tx.
usman
Gettext makes obsolete the previous in-house localization system herited from Squeak. Gettext itself is herited from Etoys. Some I guess the classes in the Pharo image are the one to be considered obsolete. But well this should be carefully reviewed. Hilaire Le 19/05/2014 12:25, Usman Bhatti a écrit :
When GetText package (http://smalltalkhub.com/#!/~PharoExtras/Gettext <http://smalltalkhub.com/#%21/%7EPharoExtras/Gettext>) is loaded in Pharo, it overwrites two Pharo classes with its own in System-Localization package: LocalID and NaturalLangaugeTranslator. Although so far I haven't seen any bugs in GetText because of this anomaly, one of the side-effects is that we get a dirty package in Monticello browser.
-- Dr. Geo http://drgeo.eu
On 19 May 2014, at 17:42, Hilaire Fernandes <hilaire.fernandes@gmail.com> wrote:
Gettext makes obsolete the previous in-house localization system herited from Squeak. Gettext itself is herited from Etoys. Some I guess the classes in the Pharo image are the one to be considered obsolete. But well this should be carefully reviewed.
Maybe we should have the get text solution in the image by default?
Hilaire
Le 19/05/2014 12:25, Usman Bhatti a écrit :
When GetText package (http://smalltalkhub.com/#!/~PharoExtras/Gettext <http://smalltalkhub.com/#%21/%7EPharoExtras/Gettext>) is loaded in Pharo, it overwrites two Pharo classes with its own in System-Localization package: LocalID and NaturalLangaugeTranslator. Although so far I haven't seen any bugs in GetText because of this anomaly, one of the side-effects is that we get a dirty package in Monticello browser.
-- Dr. Geo http://drgeo.eu
It will ease a lot of things but is it really the right things to do? (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
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.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
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/Prepa... ). 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
As long as we keep it external to Pharo I will say it is good practice. But, I am so short in time now, I hope to have more time in a few weeks. Hilaire Le 20/05/2014 10:10, Usman Bhatti a écrit :
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?
-- Dr. Geo http://drgeo.eu
participants (4)
-
Hilaire Fernandes -
Marcus Denker -
stepharo -
Usman Bhatti