I'm asking this title question quite purposely and provocatively. I have just encountered two web pages that - in my opinion - contradict each other. And what I'm seeking is your opinion and advice how to set up a site with regard to the problem.
First off - the problem.
What I want to achieve is best described on the project page of pathauto_i18n_taxonomy module - the goal is to stamp one of my content type with URL aliases that contain a term reference field, as in [node:field_genre:name]/[node:title].html:
www.url.com/de/hund/alt/hund-1.html
www.url.com/en/dog/old/dog-1.html
www.url.com/fr/chien/agee/chien-1.html
where the part: /dog/old/ is an i18n alias of the taxonomy the content type is stamped with.
Now this page seems to claim that this kind of URL scheme is not correct from the analytics and webmaster's point of view. (Sorry if I have not understood that article properly.)
What brought me to searching the net is the problem I'm having. After installation of pathauto_i18n_taxonomy I'm getting well-localized aliases for the terms alone:
www.url.com/de/hund/alt/hund-1.html
www.url.com/en/dog/old/dog-1.html
www.url.com/fr/chien/agee/chien-1.html
but mixed ones for the nodes:
www.url.com/de/dog/old/hund-1.html
www.url.com/en/dog/old/dog-1.html
www.url.com/fr/dog/old/chien-1.html
Notice that the term part is stuck at English (which is set as the source language on my site). And I believe this is a bug (Token or Pathauto?), and by no means is this a good UX.
Now the paradox I'm seeing is: IF this sort of aliasing is not correct from a webmaster's point of view, THEN why would anyone bother writing i18n modules and expand the Pathauto patterns form with i18n options?
Has anyone managed to get properly localized aliases using i18n term reference field in it? What are your insights on the problem?
