Sven Van Caekenberghe wrote: > Perfect! Well done & presented (as usual ;-)
I18N is nothing fancy, but thanks. Hope it is usefull for others too. > The way I see it, that is all there is to it. Yes - at least it solved my basic needs so far and maybe it helps us thinking about more internationalized applications for Pharo (or I18N the Pharo image itself) > I like it that a single image can translate into multiple languages. > > I guess some people would also like > > String>>#translated > ^ I18NTranslator defaultTranslator at: self > > I assume that the actual storage is open ended to also allow databases and so > on ? You decide where your translations come from/are loaded from. I use INIFile as it is plain simple to do. Internally I18NTranslator is nothing more than a simple object handling dictionaries. So the strings usually will be stored with the image (or flushed out and reloaded again at startup). If necessary the code can be refactored so that multiple storage backends or a cache can be added. Not on my todo list so far. Bye T.
