4. Go to Administer→Site building→Translate Interface (admin/build/translate) and you will see another column added to the table for “Taxonomy.” Note that we have three terms (each with a description) for forums (from the install profile), but right now the table is showing only one string available to translate. That’s not right. We need to get all of our strings recognized before we can translate them. 5. Remember that you must visit a page with the string(s) that you want to translate before it will register for the string search. Go back to the taxonomy administration at Administer→Content management→Taxonomy (admin/content/taxonomy). 6. Click the “list terms” link for the Forums vocabulary and then click on the Edit link for each term, where you can change the name and description. You should notice in the help text that they are localizable (for instance, “This name will be localizable”), as shown in Figure 8-35. You can simply look at the edit page and then return to the previous page using your browser’s back function.
Figure 8-35. Term name indicating that it is now localizable
7. Once you have done that for each of the terms listed, go back to the translation interface at Administer→Site building→Translate Interface (admin/build/translate.) You may notice that it still shows that only one string is translatable. This can happen when you have some content—in our case, taxonomy terms from the install profile—that was created prior to enabling the Internationalization module. Let’s force Drupal to double-check. 308 | Chapter 8: Multilingual Sites