Thanks Johan
I would like to know we could move all the system-Localization classes
to the getText package.
Or another package outside the core because we basically shortcut
completely its use.
I will look a bit around.
On 13 Sep 2014, at 10:09, stepharo <steph...@free.fr
<mailto:steph...@free.fr>> wrote:
Then what is the seaside-Getext? Is is a superset of pharoExtras-gettext?
https://code.google.com/p/seaside/wiki/Gettext
could we edit the wiki to say to load getText from PharoExtras?
So I have the impression that we could move System-Localization to
Gettext without impacting
- current users
- pharo core
- current seasiders.
In short: it’s a Seaside extension to internationalise your web app.
For application not doing web, does it make sense to use it?
No, but I don’t see how you guys complain about that. The package is
in the Seaside repo and in the ConfigurationOfSeaside3.
Can you explain the issue?
there are two issues:
- system-Localization is not used in the image because
NaturalLanguageTranslator>>translate: aString
^ aString
- when people load getText, the package get dirty because a new
class definition is installed.
Is it packaged separately?
yes.
Johan
