TYPO3 Core

AFAIK it's not possible to determine the language as early in the rendering process as this message is generated.

Setting resolution to "won't fix".

Using property message_page_is_being_generated, the whole html message may be overridden in config section of TS template setup. Moreover, this can be done based on a language condition. Hence, there must be a way to determine the language to be used.

The property message_page_is_being_generated forces to override the whole HTML message, not just the text . A property like message_page_is_being_generated_text may allow to translate in TS setup, but then, why not do it through normal translation mechanisms?

The typoscript config array is available at this point, but no language stuff has been initialized so far.

I think message_page_is_being_generated was not usable at all until now, so I guess I can just switch it instead of adding another new property once again.

Agreed?

I was able to use message_page_is_being_generated. The problem is that it overrides too much. Therefore I had to modify tslib_fe. Anyways, reusing it is fine with me.

But, then, why not use the normal localization mechanism in order to translate this message?

Hi Stanislas,

But, then, why not use the normal localization mechanism in order to translate this message?

I have no time to check it but think that $GLOBALS['LANG'] does not exist at this point. Can you please check that? In this case I think it would be fine to get the default text from a translation file, depending on the value of the configured language.

You're right, Michael. Language and locale are set, but $GLOBALS['LANG'] is not yet available at that point. So, it has to be done through TS setup.

Fixed in CVS, see ChangeLog for details.