[aida] Localization

[Nicolas Petton]

Hi all,

There is currently no localization support in Aida/Web. I'm currently
working on a french site made with Scribo under Squeak, and then I have
two choices:
- Manually translate all strings in french (ouch!)
- Add #translated to all strings I want to translate and translate them
with the Squeak localization support.

Both choices are bad. I need to manually change the code.

So, I think that a localization support in Aida would be really great.
It wouldn't be very difficult, but would take some time. At the end we
could have Aida and Scribo in many languages!

What do you think?

Cheers!

Nico
--
Nicolas Petton
http://nico.bioskop.fr
___
ooooooo
OOOOOOOOO
|Smalltalk|
OOOOOOOOO
ooooooo
\ /
[|]
--------------------------------
Ma clé PGP est disponible ici :
http://nico.bioskop.fr/pgp-key.html

[Nicolas Petton]

Janko,

I thougth about your idea.

Inline editing is more complex than it looks like because of Aida
structure (components, webstyle, etc), so I would leave it for later.

For symbols, I don't know if it's a good idea, because it's not obvious
at all, and it will be very tricky and intrusive! I would instead use
something like:

self translate: #welcome

and then we keep the symbol, and at least you immediately know what's
going on (I'm thinking about newcommers).

For storing, I would do as we do for css in WebStyle, ie use a
convention. For example in a WebApp class, all methods beginning with
translation are translating methods, then follows the language, and then
the view name. For example:

#translateFrMain for the translation in french of view main
#translateDeEdit for the translation in deutch of view edit

and each translation method would return an collexion, like this:

#translateFrMain
^(#welcome 'Bienvenue'
#login 'Connexion'
#bye 'A bientot'
#logout 'Déconnexion')

This way translations are easy to write and maintain.

What do you think?