Translating vocabulary names everywhere

Same problem!
i18n 6.x-1.2
drupal 6.14

The same problem. Cannot translate vocabulary names.

i18n 6.x-1.2
drupal 6.14

i work with i18n 6.x-1.1 and there vocabulary names can be translated so i suppose it should work in 6.x-1.2. (maybe a bug?)

make sure to enable 'Taxonomy translation' module

translation can be done in ' /admin/build/translate/search ' -> select taxonomy.
or you can use the translation table module at http://drupal.org/project/translation_table

does this has something to do with #64004: Integration of i18n and views.module = fix translatablity of views?

from i18n's handbook page:

This is an ongoing work and it is a known fact that i18n's views support is far from complete so better than posting (yet another, duplicate) "I want better Views integration" feature request, you can comment on the existing one, #64004: Integration of i18n and views.module = fix translatablity of views Patches are welcomed though.

@#5 nevertheless that issue was closed stating:

The original issue is fixed. Easier to pursue new ones in separate issues.

so probably this should be an ongoing issue by itself

reviewing the code (didn't debug it)

--> i18ntaxonomy_form_alter (default case)
--> i18ntaxonomy_node_form ( if ($vid == 'tags') {...} elseif (is_numeric($vid) && i18ntaxonomy_vocabulary($vid) == I18N_TAXONOMY_LOCALIZE) {...} )
--> i18ntaxonomy_vocabulary_form (return _i18ntaxonomy_term_select(check_plain(tt("taxonomy:vocabulary:$vid:name", $vocabulary->name)), ...);)

@#8 now, that seems to be only for <select> widget

when it is free tagging I don't see vocabulary name translated

function i18ntaxonomy_node_form(&$form) {
  ...
    if ($vid == 'tags') {
      // Special treatment for tags, add some help texts
      foreach (element_children($form['taxonomy']['tags']) as $vid) {
        if (i18ntaxonomy_vocabulary($vid) == I18N_TAXONOMY_LOCALIZE) {
          $form['taxonomy']['tags'][$vid]['#description'] .= ' '. t('This is a localizable vocabulary, so only terms in %language are allowed here.', array('%language' => language_default('name')));
        }
      }
    }
  ...

am I missing something?

I assume this also depends on which translation option is used:

- none
- localise (I18N_TAXONOMY_LOCALIZE) - localizable vocabulary
- per language (I18N_TAXONOMY_TRANSLATE) - fully multilingual vocabulary
- set "language to vocabulary" (I18N_TAXONOMY_LANGUAGE) - fixed language vocabulary

For option "set language to vocabulary" the translation issue might not be relevant, strictly speaking, as there is no coordinated translation - just different language taxonomy sets, switching according to assigned languages. For option "localise", I can't really say, since I'm not localising.

Option "per language" should be fully multilingual (I'm using this one). In order to be able to assign the different language terms' translations to each other, the vocabulary language should _not_ be defined (at least, this is how I understand it). For this setting, the string translations made for vocabulary name and help text do not appear in create/view/edit pages when the language is switched. This for both standard (page/story) and contrib module content.

Shouldn't the code relate in one or another way to...

taxonomy:vocabulary:$vid:name
taxonomy:vocabulary:$vid:help

There are some instances in i18ntaxonomy.module. But this is as far as I get on my own (I don't know how to code php).

By the way, others are experiencing this issue as well: [#313268] (first three comments Feb-April 2009 [not resolved]).

subscribing

subscribing

subscribing...

Guys, please test this with i18ntaxonomy 1.2.

Basically code in this patch translates the vocabulary name and help string if translation mode is set to "Per language term".

If you want to apply this to 1.3, change tt() function to i18nstrings() as code in 1.3 was refactored.

who can talk about different use case of different mode of taxonomy translation ?

I found that, per language terms mode, the translation term will have different term id.
Is there any SEO issue ?

subscribing...

Cleaning up the issue tracker. Closing all issues that haven't got any follow up for the last year.