[TYPO3-ect] translations with lib/div

[Elmar Hinz]

Hi,

> We  could try to abuse a COA as configuration carrier, so that it can be 
> referenced. Mayby that works.
> 

This does not work. I tested. So I don't have an Idea for a smart solution.
All 3 solutions have disadvantages.

1.) Classical

Def: One configuration per plugin and common constants.
Pros: Programming as usual. 
Pros: Easy to confiuge in TS templates.
Cons: Much typing because of redundant configurations.

2.) By copy

Def: Common configuration is copied to each plugin.
Pros: Programming as usual. 
Pros: Few typing.
Cons: Confusing to configure in TS templates, because of copy limitations.

3.) By setup path

Def: Configuration is taken from $GLOBALS['TSFE']->tmpl->setup.
Pros: Few typing. 
Pros: Easy to confiuge in TS templates.
Cons: Programming is different. Needs additional setup path.
Cons: Confusing merging procedure with main() config.