Translation of forums (via taxonomy terms + string translation) being ignored

I've been trying to solve this for weeks now.. many posts I googled refer to D5, or are imprecise.

I also bought the UsingDrupal book and in chapter 8 its explained how to setup a translated forum, but that doesn't work either. No explanations in the book's forum either http://forums.oreilly.com/category/39/Using-Drupal/.

Just noticed: If a forum is reached by its tax. term, i.e. "fr/taxonomy/term/1" forum title are translated, but not if used by the forum URL, i.e. fr/forum/2.

Going into sites/all/modules/i18n/i18ntaxonomy, and doing a "grep -i forum *" shows nothing!
In fact "grep -iR forum *" a level higher shows nothing either..

Does anyone have a multilingual D6 forums running out there?

Yipee! Just found one fix in http://drupal.org/node/277689.
Since Advanced Forums in being used in this case, modify the advanced_forum_preprocess_forum_list()
in modules/advanced_forum/advanced_forum.module, to add the following on the third line of that function:

  if (module_exists('i18ntaxonomy'))
    $variables['forums'] = i18ntaxonomy_localize_terms($variables['forums'], array('name', 'description'));

With that the list of forums on the /forum page is translated.

When in an individual forum, (e.g. /forum/14), the forum name is not yet translated though.

So, my solution for the standard (core) forums modules is to add calls to i18ntaxonomy_localize_terms() to forum_nodeapi(), template_preprocess_forums() and template_preprocess_forum_list().

diff with drupal 6.14:
diff -r1.1 forum.module
184a185,187
>   // Translate 'Forums' on the forum list page
>   $vocabulary->name = t($vocabulary->name);
>
200d202
>           // Translate
>           if (module_exists('i18ntaxonomy')) {
>             $parents = i18ntaxonomy_localize_terms($parents, array('name', 'description'));
>           }
645a646,652
>
>   // Translate 'Forums' on the forum list page
>   if (module_exists('i18ntaxonomy')) {
>     $variables['parents'] = i18ntaxonomy_localize_terms($variables['parents'], array('name', 'description'));
>     $vocabulary->name = t($vocabulary->name);
>   }
>
772a780,782
>   // Translate forums
>   if (module_exists('i18ntaxonomy'))
>     $variables['forums'] = i18ntaxonomy_localize_terms($variables['forums'], array('name', 'description'));

This fixes: the container list (+ breadcrumb), and forum list within a container.

The hack in #3 is not needed in advanced_forums, if the above is applied.

Although this works, I still find it hard to believe its necessary to hack core to get forums translated... there must be a more elegant and upgrade-compatible way..
If forums was not in core, or implemented as objects, then maybe overriding functions would be easier..

One idea would be to fix upstream in modules/taxonomy/taxonomy.module, in taxonomy_get_parents() and taxonomy_get_vocabulary(). That would benefit other modules using taxonomy and not just forums.
Once again its a core hack though... I'd like the opinion of a experienced Drupal developer on where this should be fixed..

Just found a patch to i18ntaxonomy (committed on 4th.Aug.09 not yet in the stable release), http://drupal.org/node/531710, which overrides _nodeapi.
Applying this patch does not solve the forums/containers/breadcrumbs translations for me though.