Glossary to work with i18n

See #258843: i18n support for Drupal 6.x for work being done inside the Glossary module. Glossary worked fine for 5.x (see #233688: i18n support), but appears to have lost functionality in the shift to the new system of 6.x.

I am the Glossary maintainer. I suspect this should actually be a support request. I just need to know how to identify which term is which language, if that is possible.

It depends on the choice of language options for vocabulary. Under the translatable choice, each term has language set in term_data under the setting "language".
Example from my table:

INSERT INTO `term_data` (`tid`, `vid`, `name`, `description`, `weight`, `language`, `trid`) VALUES
(2, 2, 'NŠ', 'Primary School', 0, 'en', 1)

where N≈† = NŠ

Edit: And there's a function to check for translations:

/**
 * Get translated term's tid
 * 
 * @param $tid
 *   Node nid to search for translation
 * @param $language
 *   Language to search for the translation, defaults to current language
 * @param $default
 *   Value that will be returned if no translation is found
 * @return
 *   Translated term tid if exists, or $default
 */
function i18ntaxonomy_translation_term_tid($tid, $language = NULL, $default = NULL) {
  $translation = db_result(db_query("SELECT t.tid FROM {term_data} t INNER JOIN {term_data} a ON t.trid = a.trid AND t.tid != a.tid WHERE a.tid = %d AND t.language = '%s' AND t.trid", $tid, $language ? $language : i18n_get_lang()));
  return $translation ? $translation : $default;
}

I did just see your response to http://drupal.org/node/233817. 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.

If you have a "language" column in term_data, then they have done something that is largely considered a no-no in Drupal. There is no "language" column in my term_data table, so they had to have modified a core table.

As for calling functions to translate, I am extremely reluctant to do so. Glossary is already performance-bound and more calls and queries is too likely to push it over the edge and make it unusable.

Wrong queue to assign it to myself

#258843: i18n support for Drupal 6.x