Taxonomy Translation
| Project: | Pathauto |
| Version: | 6.x-2.x-dev |
| Component: | I18n stuff |
| Category: | feature request |
| Priority: | normal |
| Assigned: | Unassigned |
| Status: | duplicate |
Jump to:
Hi, I'm using i18n with pathauto on my website.
Here's what I want to do:
I have a taxonomy which is set to "Localize terms. Terms are common for all languages, but their name and description may be localized."
So when I create a term, and assign that term to an English node. After translating that node to Turkish or some other language, all I need is to translate that term using locale module.
Here is an example;
As you can see, the term given to that node is "blog", if you check it's Turkish translation, the term is "günce".
Now, my problem about the pathauto is this:
if I create an automated URL like [termpath-raw]/[title-raw]
the [termpath-raw] for the both of them is created as "blog".
What I need is to have some variable like [termpath-i18n-raw] which will create the translation according to the language of the node. Then I will be able to have some stability on language of the URLs like;
[code]
http://tr.koray-al.com/gunce/ted-talks-ve-turkiye
http://en.koray-al.com/blog/ted-talks-and-turkey
[/code]
instead of;
[code]
http://tr.koray-al.com/blog/ted-talks-ve-turkiye
http://en.koray-al.com/blog/ted-talks-and-turkey
[/code]
#1
+1
This would be also an excellent feature for multilingual sites from a SEO point of view
#2
Subscribe
To the description "Localize terms. Terms are common for all languages, but their name and description may be localized."
they should have added "but it is absolutely useless/not working for pathauto" ! This would avoid one thinking it is a (his) configuration problem and waste hours trying to figure out.....
There seems to be some sort of solution at http://drupal.org/node/290421 through a patch, but if even the most simple things through Drupal are confusing I wouldn't dare trying patches.
I find Drupal absolutely NOT at all to be as prepared either for multilanguage or multisite as much promoted... It's full of small bugs and pending issues, specially when trying to plug things together. It is not at all smooth for any non-extremely-advanced PHP/Drupal freak and newbies can, no WILL, loose months off their live trying to overcome incompatabilities through trial and error as I did (still doing :( It drives you crazy.
If you haven't started with Drupal yet my recommendation is DON'T, stick to plain HTML. The supposed advantages don't compensate the loss of time in trying to understand. When you work in HTML each time you make a page, at least your sure it's there, with Drupal you're never sure.
#3
Days have gone by and I think by now I have tried everything possible, at least for me.
And of course no progress, as is normal under Drupal.
I found this patch http://drupal.org/files/issues/290421.patch
I don't know anything about patching and of course there is no understandable step by step explanation for newbies to be found, but fortunately through http://drupal.org/node/34422#comment-75030 (very old) I understood the "-" lines just could be substituted by the "+" lines which I did manually. Fortunately nothing stopped working, but it neither did what it was supposed to do: generate term-translations for Pathauto.
However, this patch does not say where source and translated taxonomy terms should be defined, I deduced Translation Table but I'm not sure. (http://drupal.org/project/translation_table): admin/build/translate/table/taxonomy
I have a Spain-dedicated web in 4 languages, with subdomains for each destination e.g.: sevilla.spain-domain.com, granada.spain-domain.com and costadelsol.spain-domain.com. Each with it's corresponding /en, /nl, /it and /es directory for language definition.
Under taxonomy I have tried both the "localize terms" and "per language terms" settings:
When using "localize terms" no translation seems to be applied (I suppose that's what meant by "Terms are common for all languages", but then what's the sense of "name and description may be localized"....?¿?). What DOES happen is that if you start in english, the term is 'monuments and buildings'. Doing next the Italian version for example, under the taxonomy one can choose between the original term in english or the translated term in Italian. On choosing the translated term, all the other languages end up using "monumenti ed edifici" as well.
So this is not useful.
Strangely, when using "per language terms" ......I get the same result.
This is so confusing..
Now I suddenly discover that the terms have all disappeared from the Translation Table. They were there before under Taxonomy. No idea how to get them in there again....
All this loss of time to try to get something working which should have been Core! What else could be the reason of being Multilanguage??
Ah yes, Menu Titles (not items) per language, which is not possible either.
#4
Sub
#5
Marked this as a duplicate of #290421: When i18n is installed support localized taxonomy
#6
Sub