May 2010 - Pharo-dev - lists.pharo.org

Re: [Pharo-project] gettext package

by Hilaire Fernandes

The gettext package is in the http://www.squeaksource.com/PharoInbox

May 1, 2010

Re: [Pharo-project] gettext package

by Hilaire Fernandes

Thanks to the virtual hacking session yesterday on IRC (irc.freenode.org #pharo-project) and the help of hackers Marcus, Henrik and Korakurider we have moved the gettext package in a workable state. So far .po files can be exported as domain (class category) for translation and .mo (compiled translated message) are imported at Pharo startup. Still there are thing to do and discuss: - I have moved all the modified and added classes in the gettext package. Modified classes were moved out of their original category, for example LocaleID, NaturalLanguageTranslator. If we want to group translation tool it mean recatgorisation in the core Pharo. - If we want the gettext package to be loadable, the method String>>translated in core could be changed to return self, then the gettext packaged provided the translated version to effectively handle the translation. - regarding translation, we could end with a pharo.po file to group the translated message of the core. It will be located in a folder locale along the image. There are still cleaning to do in the internal, and I hope simplifications in the code. Hilaire Hilaire Fernandes a Ã©crit : > I have move in a Gettext package in PharoInbox classes for gettext > support. Do not expect it to work. Some of the classes there, are just > moved from former categories in pharo System-Localization and > Multilingual other are coming from Etoys. > > I have not yet test to load it in a fresh image. > > Hilaire

May 1, 2010

Re: [Pharo-project] Issue 2372: HelpSystem for 1.1

by StÃ©phane Ducasse

> > Hi, > > The help core package and the according tests package are ready for > integration in the pharo inbox. After talking today with Stephane I also > removed the squeak specific stuff, so it is ready for inclusion in > Pharo 1.1. core image. > > The idea is to have the basic help support (help core) in the Pharo > core image and provide additional docu/help books in the dev-image. for now this is more important to add documentation and since help is easy to unload. I would put helpcore into core + help into dev In the future we may move it outside mini. thanks torsten. Let see what the other think. > > But this should depend on a community decision, so any comments > would be appreciated. > > A second option would be to to keep it out of the core image > and just provide the help support and documentation in the > Pharo-dev image. > > Bye > T. > > > -- > GRATIS fÃ¼r alle GMX-Mitglieder: Die maxdome Movie-FLAT! > Jetzt freischalten unter http://portal.gmx.net/de/go/maxdome01 > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

May 1, 2010

Re: [Pharo-project] Xemina Pharo, HÃ ná»i, Viá»t Nam

by Serge Stinckwich

2010/4/29 Torsten Bergmann <astares(a)gmx.de>: > Hi Serge, > > nice demo! Looking through the slides in "Build you own control > structure" you use #ifSeven: as example which is easy, but not a > "real world use case". > > I typically use another example: > > In a few languages you have a "REPEAT (block) UNTIL (cond)" control > structure (in Pascal for instance) which is easy to add to Smalltalk > with a #repeatUntil: method on BlockClosure. Yes your example is nice. Thank you Torsten, for your comment. -- Serge Stinckwich UMI UMMISCO 209 (IRD/UPMC), Hanoi, Vietnam Every DSL ends up being Smalltalk http://doesnotunderstand.org/

May 1, 2010