[TYPO3-ect] translations with lib/div

[Elmar Hinz]

> 
> ok, i got it.
> Anyway defining a global setup only for copy might misleading by searching
> for configuration in ObjectBrowser.
> This could prevent by using a tempObject for copy.

Yes. Or just do it the classical way, with an own setup for each plugin and
common constants. Well, I start to repeat me.

> In Bananas also the naming plugin.tx_bananas.configurations is misleading
> for configuration, but this is only maculation (but it costs me lot of
> time)

I would say, it took time to understand the general implications of the TS
copy command. We all have to make this experience at a different point,
i.e. when trying to alter css_styled_content, to improve the rendered
output.

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

> 
> So back to topic: what would you prefer, a method like
> $translator->_LOCAL_LANG =$this->configurations->get('_LOCAL_LANG.');
> 
> or do you see a possibility to access it direct from translatorclass?

The second. I think it should work automatically, without additional
function calls. That's already standard in tslib_pibase, 

Regards

Elmar