Re: [Pharo-project] Gettext package?
On May 25, 2011, at 11:03 AM, Henrik Sperre Johansen wrote:
On 25.05.2011 08:14, Marcus Denker wrote:
On May 24, 2011, at 11:13 PM, Hilaire Fernandes wrote:
I ported the gettext package from Etoys to Pharo with help of other (Henrik). I have to admit I mostly forgot about its internal, even if I amn using it for DrGeo. In between, some part of the gettext package in Etoys was improved, I forgot which part exactly. Bert may remember a bit more.
Do whatever you think is appropriate with the package. As you hacked the package recently you are definitely in a better position to split it in different component.
Right now there is support for internationalisation in the image.... but not really used. Would it make sense to replace that with Gettext? (and make gettecht a core feature?)
Marcus
If you mean String >> #translated, the previous localization functionality in NaturalLanguageTranslator has been replaced by stubs since 1.2. The System Integration part of gettext package I mentioned hooks into this, and is the expected thing to use for those needing it.
Personally, I don't think it belongs in Core.
But does it belong into that what we call Pharo? -- Marcus Denker -- http://www.marcusdenker.de INRIA Lille -- Nord Europe. Team RMoD.
On 25 May 2011, at 11:34, Stéphane Ducasse wrote:
But does it belong into that what we call Pharo?
yes probably.
If you want to keep and improve the existing "localisation & translation" support, I think it's a good idea to integrate Gettext. It uses a format that is used beyond the Smalltalk community. But I guess the above depends wether the 'core' Pharo tools require some "translation" support. And I don't think they do, i.e: I don't think we want a french version of the system browser ;-) They might require "localisation" without the translation (i.e. date format etc.) but Gettext is not about that. Any internationalization support is more a package to be used by applications developed in Pharo. My use of Gettext, for example, is for translation support in Seaside apps. Hilaire uses it for Dr. Geo. Of course, GemStone and Visualworks also come with an internationalization library integrated in the basic image (not entirely sure about VW). If I do more work using Gettext, I can certainly do something for its integration in Pharo. Johan
If you want to keep and improve the existing "localisation & translation" support, I think it's a good idea to integrate Gettext. It uses a format that is used beyond the Smalltalk community.
yes
But I guess the above depends wether the 'core' Pharo tools require some "translation" support. And I don't think they do, i.e: I don't think we want a french version of the system browser ;-)
:)
They might require "localisation" without the translation (i.e. date format etc.) but Gettext is not about that. Any internationalization support is more a package to be used by applications developed in Pharo. My use of Gettext, for example, is for translation support in Seaside apps. Hilaire uses it for Dr. Geo.
Of course, GemStone and Visualworks also come with an internationalization library integrated in the basic image (not entirely sure about VW).
If I do more work using Gettext, I can certainly do something for its integration in Pharo.
excellent so let us know.
Johan
participants (3)
-
Johan Brichau -
Marcus Denker -
Stéphane Ducasse