Ok I'll try to explain:
As
first step I activate Translate for the print_header() and print_footer() functions (represented by MyTheme/header.htt and MyTheme/footer.htt).
In this two templates you can use any of the translation definitions from wb/languages/XX.php and MyTheme/languages/XX.php too.
i.E.:
in EN.php you have the definition:
$TEXT['SOME_TEST'] = 'This is a test'; so in the templates you can display it using
{TEXT_SOME_TEST}You need a completely new translation?
insert
$MESSAGE['HELLO_AGAIN'] = 'BliblaBlubber..ups'; into your language file.
insert
{MESSAGE_HELLO_AGAIN} into your template. That's all...
As
second step am working on is to activate Translate for all addons inside the
wb/admin/ folder.
Then each addon can(but must not) have it's own
languages/ folder. Here all addon depending translations will be stored. Independent from the theme which is in use.
As
third step Translate becomes an additional functionality to load language files from active theme or active template (depending from Front- or Backend)
The final result shall be:
Basically Translate loads definitions from
wb/languages/ then overwrite/extend this loading definitions from
admin/addon/languages/then again overwrite/extend this loading definitions from
MyTheme/languages/ or
MyTemplate/languages/The resulting list then is available to use in *.htt files.
So by default you have all translation definitions from core and the active addon available.
If you need personalized definition in your theme, so add the folder languages/ to your theme and place all language files ( XX.php) into it. Here you can overwrite any previous definition from core or addon. Also you can add completely new, additional definitions.
Any questions more?

no problem, i can answer it.
But remember: with Revision 2094 step_1 only is finished yet. The next steps will follow as soon as possible.
Manuela