So I'm checking and when we load Gettext,
System-Localization only contains
ISOLanguageDefinition
Locale
Locale is used by LanguageEnvironment, LocalID, TimeZone, Unicode
When we will clean leadingChar some of these will go away.
So not all the package System-Localisation can be moved out the image to got in
a newer version of getText
Localization is very basic functionality that should be provided by the
platform itself.
To me it was not that obvious.
We are in the situation that we are in only because people see Pharo as
something “to build on top”.
This way everyone does their own I18N stuff, while the right thing would be to
have *one* that is good and
part or Pharo itself.
Frankly do you want to have menu in german?
I would really like to avoid to have String poluted with translation.
Translation of external string have not really something to
do in a language core.
Just think about it: Pharo itself should have translated menus.
Really.
Who would be using them **AND** maintain their translation.
So we need *something* in the system anyway.
Why then not make it good and make it the one that everyone is using?
May be but not by forcing all the internationalization code to be in the
bootstrap because it is not its place.
I would like to get the leadingChar cleaned and use Unicode and we could
get rid of a lot of strange code.
Marcus
