If you visit my website and try out the following pages:

http://blog.vogol.com/en/taxonomy_vtn/term/29
http://blog.vogol.com/nb/taxonomy_vtn/term/29

You will notice three things:

  1. On the English page there are no nodes, it should make a note in the text that i18n is turned on and that the translated page might have nodes
  2. On the Norwegian Bokmål page the term name isn't translated. It seems #279060: Internationalization and localized terms hasn't made it into the latest release. Never mind that I haven't translated the internal Drupal strings (yet)
  3. On both pages it would be nice to have a link to the other languages available for that page; just as a node has links to translations of itself.

Comments

pkej’s picture

pkej commented

Ah, there also are similar problems with the following pages:

http://blog.vogol.com/nb/taxonomy_vtn/voc/1
http://blog.vogol.com/en/taxonomy_vtn/voc/1

The translated terms are not showed on the nb page.

AlexisWilke’s picture

AlexisWilke commented

pkej,

My experience with i18n is really bad. At this time I have turned it off from all my sites simply because I just cannot stand it. Nothing works right with it. The whole of Drupal has a totally wrong approach to translation. Way too complicated. I just could not imagine explaining that to my customers!

Now, if you provide a working patch, I'll be happy to apply it.

I'm actually surprised that it already works so well (i.e. that only English or Bokmål text shows up).

Thank you.
Alexis

pkej’s picture

pkej commented

I will try to look into it.

It might be better to make it a separate module, i18n_taxonomy_vtn, and let that one go in and hook in and filter the output from taxonomy_vtn. Is that possible, you think?

pkej’s picture

pkej commented

The i18n in v6 seemed very well, until yesterday, when I did some changes to my blog, and it suddenly started to reject translations of nodes. I think it is when I write in Norwegian first, but I will have to look into it.

For taxonomy the translation_table module is a heaven sent, it works very well, and took care of the main gripe in 5.x.

AlexisWilke’s picture

AlexisWilke commented

pkej,

An additional module would be a good idea to avoid having i18n dependencies in taxonomy_vtn itself.

Although, it could be a sub-module (i.e. taxonomy_vtn/taxonomy_vtn_i18n/taxonomy_vtn_i18n.module)

And if you need some callbacks, let me and I'll ad them in taxonomy_vtn (i.e. like to add the language links somewhere).

Thank you.
Alexis

AlexisWilke’s picture

AlexisWilke commented

pkej,

Is this still a problem for you? Or can we close the issue?

Thank you.
Alexis