Is there any specific reason, why this action outputs a header since 1.1.6.2? Do I have to search in recentlycommented.php for the header to change it or is there any simpler way of changing it? It _is_ somewhat annoying to have english headers on a german web page which cannot be changed in a simple manner ... :-(

Masin, the idea is precisely to enable easy translation of GUI strings without forcing our users to hack the code. The new version of recentlycommented is meant to:
1) make headings more consistent across different default Wikka pages;
2) make them configurable as defaults, for i18n purposes.

Currently the recentlycommented actions contains the following i18n string:

if (!defined('RECENTLY_COMMENTED_HEADING')) define('RECENTLY_COMMENTED_HEADING', '=====Recently commented pages=====');

As soon as a basic routine is available to handle localized strings, you will just need to modify your custom value for RECENTLY_COMMENTED_HEADING (e.g. in a file called lang/wikka.de.php) which will override the English defaults declared in the action.

Hope this is clear enough. If you need a localized heading as of 1.1.6.2 you can just modify the value of RECENTLY_COMMENTED_HEADING in the action itself.

I feared as much ... okay source code, here I come!

Okay, after having changed all text in the RecentThree, there's one question still pending: Why do they output headings? Thes are actions, meant to generate content to be put somewhere on a page. Somebody might want to create his own version of a page, where all information is stored (see my user page for example). Am I the only one thinking, that more than one top most heading is too much? Perhaps such translations should occur at setup time and the corresponding pages already get stored with the language selected ... wikka.de.php wouldn't just include the i18n strings but some kind of setup steps, which pages should be initialized which way.

RECENT_COMMENTS_SETUP_STRING='=====Kürzlich kommentierte Seiten=====\n{{RecentlyCommented}}{{nocomments}}\n\n\n----\nCategoryWiki'

Of course, it would be nigh to impossible to change the language setup at a later time without losing all custom modifications to the standard pages, but it would give more flexibility to those who wish to design their own page flow. Alternatively, why not just allow a parameter h='x' for these actions, where x means
0: no heading
1: ======
2: =====
3: ===
4: ==

But this way as the current implementation doesn't allow LinkUsingPageTitle to work properly 'cause there's no heading in the page code :-(

Masin - I agree, headings should be inserted as content in default pages, and not be part of the action itself. Would you mind opening a ticket on this point as a reminder? Once i18n support is available, we will be able to provide an option to decide during installation which set of (localized) default pages to create.