Reminder from #258843: i18n support for Drupal 6.x to update documentation of using Glossary in different languages.

Comments

nancydru’s picture

Title: Update Documentation on i8n » Update Documentation on i18n

Thank you.

nancydru’s picture

Status: Active » Postponed (maintainer needs more info)

Please check out http://drupal.org/node/201763 (at the bottom).

AaronCollier’s picture

After some more testing, I have some new conclusions. This is partly because I had been using the abbr tag without a link, so it was not normal use cases.

Yes, it works with Set language to vocabulary.

With Localize terms, I get only English definitions in both languages. If I click on a link, it will show me the English definition, even if I have selected a Czech Language Page.

With "Per language terms" I have to create definitions in both languages and adding a "Translation" does not help me at all. The definitions do not appear to be linked together in the glossary.

I'd say there must be some bugs with i8n or something. I could try to figure out what, but I don't know.

For now, I'd write the documentation like this:

<h3 id="languages">Languages</h3>
<h4>Drupal 5.x</h4>
<p>(From http://drupal.org/node/48966) In your settings.php file you must insert something like the following:<br />
<div class="codeblock"><code>$conf['i18n_languages']['locales'] = array(
  "pt-br" => "pt_BR.UTF8",
  "fr" => "fr_FR.UTF8",
  "en" => "en_US.UTF8",
  "es" => "es_ES.UTF8");<end the code><div><<br />
The actual content depends on the languages you use and locales you have installed.</p>

<h4>Drupal 6.x</h4>
<p>If you want your definitions to only appear in one language (and not any others you have running on your site), you can set the Vocabulary you are using to "Set language to vocabulary" and then define a language for your terms.</p>

<p>If you would like to have your terms be defined in more than one language, you must set the Vocabulary to "Per language terms" and for each term you can set the language. To have a term appear in two languages, you need to create two terms, one set to each language.</p>

By the way, the XHTML in front of Firefox Tool Tips and Languages is rather strange. They have empty anchors and rel="nofollow", while the other sections don't.

nancydru’s picture

The documentation is updated.

I don't think rel="nofollow" is coming from this module, so the rest of that is suspect as well. But is this somewhere that I can see it?

AaronCollier’s picture

Sorry I was unclear. I just meant in the documentation. Visible through View Page Source.

nancydru’s picture

Oh, the empty anchors are named anchors for pointing to from issues. And DO inserts the rel=nofollow automatically even though it's meaningless there.

nancydru’s picture

Status: Postponed (maintainer needs more info) » Fixed
AaronCollier’s picture

I just thought it was strange that the other sections used the headings as anchors, while these two sections inserted meaningless extra code. You now have two things linked to "languages" - the anchor and the header.

nancydru’s picture

Okay, I think I fixed that.

Anonymous’s picture

Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for two weeks with no activity.