I am currently not getting i8n support in Drupal 6.2. I have terms that exist in two languages, English and Czech. I have connected the terms with the translate option of the taxonomy. But I only see the English option even when the page's language is set to Czech. Terms that are only in Czech appear in Czech, but terms in both appear in English. It would be nice to be able to see only Czech things.

Since the hardworking and dedicated NancyDru is unavailbe for this issue, and not much help is appearing from the i8n folks, I'm not sure how it will get solved. Is anyone familiar with how i8n works in relation to this module?

Comments

nancydru’s picture

nancydru
she/her/hers
Primary language English
Location Boston
commented

See also http://drupal.org/node/233688.

I'm not unavailable, I just don't speak any languages other than English, so I don't have a site or any experience with i18n. It took a lot of user input and testing to get i18n working with 5.x. I'm disappointed that we seem to have to start all over again with 6.x.

AaronCollier’s picture

AaronCollier commented

Sorry, I just meant unavailable in the sense of testing and such. Version 6 changed the fundamental way Drupal relates to languages and the locale module. Some parts were moved to core. It's a lot different module from what I hear.

Of course, it might just be my setup, though this in the i8n cue seems to say it's not: #256415: Glossary to work with i18n.

nancydru’s picture

nancydru
she/her/hers
Primary language English
Location Boston
commented

I just committed a change to all my db_rewrite_sql statements so they will hopefully get seen by i18n. This will be in the -dev version shortly. It was unnecessary in 5.x. Since I don't have i18n, you will need to tell me if it works any better.

nancydru’s picture

nancydru
she/her/hers
Primary language English
Location Boston
commented
Status: Active » Postponed (maintainer needs more info)
AaronCollier’s picture

AaronCollier commented

Great, now it works just fine. Thanks a lot.

I'd change the status to fixed, but the documentation really ought to be fixed too. For one thing, this only works with vocabularies that are "Per language terms" and not with vocabs set to "Localize terms"*. (I assume it works with "Set language to vocabulary", too, but I haven't tried that.) So it'd really be good to have documentation that said this. The current documentation is only valid for 5.x.

I'm not sure whether to open a new issue for documentation or just change the status/component here. I could try to write something for the documentation, but not today.

* I think this would require the translate functions, which you are right not to want to add to this module. But I could be wrong about that.

nancydru’s picture

nancydru
she/her/hers
Primary language English
Location Boston
commented
Assigned: Unassigned » nancydru
Status: Postponed (maintainer needs more info) » Fixed

Fabulous. I'm glad it was that simple to fix. I would just as soon have the documentation opened as a new issue. The documentation is really pretty much for both 5.x and 6.x; I don't think I've added anything that is release-specific (yet).

nancydru’s picture

nancydru
she/her/hers
Primary language English
Location Boston
commented
Title: i8n support for Drupal 6.x » i18n support for Drupal 6.x

Just noticed a 1 missing in the title.

Anonymous’s picture

Anonymous (not verified) commented
Status: Fixed » Closed (fixed)

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