Have a look at I18N project: http://smalltalkhub.com/#!/~TorstenBergmann/I18N/
The docu with examples and all is on the same page.
On 14 Sep 2014, at 12:59, Marcus Denker marcus.den...@inria.fr wrote:
On 13 Sep 2014, at 20:51, stepharo steph...@free.fr wrote:
So I'm checking and when we load Gettext,
System-Localization only contains
ISOLanguageDefinition
Locale
Locale is used by LanguageEnvironment,
On 13 Sep 2014, at 19:54, stepharo steph...@free.fr wrote:
On 13/9/14 15:57, Hilaire wrote:
Hello,
I guess the gettext package on the seaside repo depends on the gettext
package at PharoExtra and it adds some glue code for Seaside use. Is it
correct?
I did not check but I think so
Localization is very basic functionality that should be provided by
the platform itself. 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
Peter,
Gettext works. See DrGeo, for example.
Also, the Seaside-Gettext extension works just fine.
If I understand correctly, the Pharo IDE (and rest of the system) has not been
working with ant localization implementation.
Johan
On 14 Sep 2014, at 16:18, Peter Schorsch trala...@freenet.de
On 14 Sep 2014, at 12:59, Marcus Denker marcus.den...@inria.fr wrote:
Just think about it: Pharo itself should have translated menus. So we need
*something* in the system anyway.
Why then not make it good and make it the one that everyone is using?
Yes, and actually, Gettext is just about
Le 14/09/2014 16:49, Johan Brichau a écrit :
Yes, and actually, Gettext is just about the support for the Gettext format [1].
So, you can see it as an extension of the existing Localization system that is
already in the image and it’s probably a good idea to internalize it completely.
The
On 14/9/14 16:18, Peter Schorsch wrote:
Localization is very basic functionality that should be provided by
the platform itself. 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
On 14/9/14 16:39, Johan Brichau wrote:
Peter,
Gettext works. See DrGeo, for example.
Also, the Seaside-Gettext extension works just fine.
If I understand correctly, the Pharo IDE (and rest of the system) has not been
working with ant localization implementation.
the fallback was simply to
Marcus I think that we should sync because personally I do not want to
giant kernel. I want a bootstrap and modular packages.
I think that making all the packages internal to the image is a recipe
to get a monolithic system.
I do not see why loading a package would hurt.
Stef
On 14/9/14
Hi,
The Seaside-Gettext package is in the Seaside repository
http://www.smalltalkhub.com/#!/~Seaside/Seaside30Addons
The package in the PharoExtras repository is a relic.
The ConfigurationOfSeaside3 correctly references the Seaside-Gettext package
and it’s absolutely functional (using this in
Hi johan usman and other
I would like to get a clearer picture.
https://pharo.fogbugz.com/f/cases/13655/System-Localization-and-Gettext-have-classes-with-identical-names
We could change the name of in the PharoExtras package gettext so that
we do not have conflicts
On 13 Sep 2014, at 10:09, stepharo 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
In short: it’s a Seaside extension to internationalise your web app.
For application not doing
Le 13/09/2014 09:57, Johan Brichau a écrit :
Hi,
The Seaside-Gettext package is in the Seaside repository
http://www.smalltalkhub.com/#!/~Seaside/Seaside30Addons
http://www.smalltalkhub.com/#%21/%7ESeaside/Seaside30Addons
The package in the PharoExtras repository is a relic.
You mean the
Hello,
I guess the gettext package on the seaside repo depends on the gettext
package at PharoExtra and it adds some glue code for Seaside use. Is it
correct?
Le 13/09/2014 12:43, Johan Brichau a écrit :
On 13 Sep 2014, at 10:09, stepharo
steph...@free.fr
mailto:steph...@free.fr wrote:
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
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
I will have a look and check… (with the first goal to add an issue tracker
entry for it)
On 08 Sep 2014, at 20:01, Hilaire hila...@drgeo.eu wrote:
Marcus,
Alain's MathOntologie package provide Classes and Messages with French
accent, to ease the understanding of programming to high school
Absolutely right. I open a ticket for Alain
https://pharo.fogbugz.com/f/cases/13980/Math-Ontologie-on-Pharo-3-0.
Alain I suggest you get your hand in the Pharo bug tracker
(http://bugs.pharo.org) and create yourself an account[1] there to
comment and to report additional problem you may meet.
Absolutely right. I open a ticket for Alain
https://pharo.fogbugz.com/f/cases/13980/Math-Ontologie-on-Pharo-3-0.
Alain I suggest you get your hand in the Pharo bug tracker
(http://bugs.pharo.org) and create yourself an account[1] there to
comment and to report additional problem you may
What is the purpose of the seaside-gettext package ?
Is it a relic or is it useful? Gettext is orthogonal to Seaside.
Hilaire
Le 07/09/2014 15:32, Peter Schorsch a écrit :
But then I had to realize that the seaside-gettext package was not
installed; and also no gettext package. I found a
Hi,
I don't know if it is related but I have problems importing french files
inside Pharo 3: Anytime when there is an accentuated character there is an
error, and the file is not imported. Even if the character is a quote
inside double quotes (like in it don't work) there is an error message.
Hi Peter,
For my application needs (English - French), I normally use the gettext
package from STHub and it works without any problems for me.
http://smalltalkhub.com/#!/~PharoExtras/Gettext
GetText so far not including in the Configuration Browser but we should
include it. There is also a
Depending on your exact needs, you might be better of with the QCMagritte
based multi-language support.
https://www.youtube.com/watch?v=cTut44Xs3_U
To try download a QCMagritte image from
https://ci.inria.fr/pharo-contribution/job/QCMagritte/
start a seaside adapter
I don't know anything about Seaside or Gettext packages, however I
notice one thing (below)...
Peter Schorsch wrote:
Hi,
Just started with pharo and seaside. Now I want to write an example
seaside-application but with a multi lingual interface. So I installed
pharo3 and then seaside via
On 7/9/14 15:32, Peter Schorsch wrote:
Hi,
Just started with pharo and seaside.
Welcome!
Now I want to write an example
seaside-application but with a multi lingual interface. So I installed
pharo3 and then seaside via configuration browser.
But then I had to realize that the
26 matches
Mail list logo
