Hi,
I'm happy to see a view module for internationalization. For most site, lot of contents are generated by views, and it was a pain to translate. I hope this module will make our life more easy.
However there is a problem with the views title, especially the one generated with arguments like taxonomy_term view.
I translated my taxonomy via the locale system. When I go into a node, I can see the right translation of my term, but when I browse my node listing with taxonomy_term views, all the titles are in english (the default language), so they are not translated.
It could be very usefull to get the correct language for the title when a term is translated...
thanks
zmove
Comments
Comment #1
zmove CreditAttribution: zmove commentedI finally found the solution :
in argument.handler.inc
Replace
By:
And then, your title will become translatable viia the locale system.
Comment #2
David Lesieur CreditAttribution: David Lesieur commentedDuplicate of #64004: Integration of i18n and views.module = fix translatablity of views.
Comment #3
GiorgosKView titles are indeed translated but still taxonomy views titles (taxonomy_term) are not
I am testing with the dev of i18n and the 2.x dev of CCK and 2.x dev of views
anybody else experiencing the same ?
Comment #4
GiorgosKcan we consider this a bug
Comment #5
GiorgosKtemp solution until this is sorted
include in the header of your taxonomy_term view
input format: php
Comment #6
vnb CreditAttribution: vnb commentedsubscribe
Comment #7
tomsm CreditAttribution: tomsm commentedThe header modification of #5 works great.
But does anyone have a solution to translate the breadcrumbs, and the taxonomy term that appears under each teaser or full node?
Comment #8
mattiasj CreditAttribution: mattiasj commentedThanks for solution #5!
Comment #9
Jose Reyero CreditAttribution: Jose Reyero commentedFixed with #360024: Write views localization plugin
But needs this views patch #357529: Implement translation of customized 'translatable' views properties
Comment #11
PieterDCThanks for solution #5!
And looking forward to the patch in #9 to be included in an official release.
Comment #12
gzveri CreditAttribution: gzveri commentedAdd this in the view header, and set input type to php code:
Comment #13
skat CreditAttribution: skat commentedhow do you add that code in the view using views 3.0? thank you very much!
Comment #14
selinav CreditAttribution: selinav commented#5 and #12 don't work
I've always title in french.
subscribe
Comment #15
GiorgosK#14
Put english as your default language
and translate to french
make sure the string become translatable by visiting page in french or refreshing the strings
Comment #16
selinav CreditAttribution: selinav commentedIs it dangerous to change the default language on a production site?
Comment #17
czaku CreditAttribution: czaku commentedI embedded that code in header and receive errors with tt() function (doesnt exist)... could you please help me?
Comment #18
GiorgosKThose are all temp solutions did you try #5 ?
a different setup would be entity/entity_translation/title/i18n modules that might do the trick
Comment #19
czaku CreditAttribution: czaku commented#5 didnt work, I use D7, #12 makes an error :/
Comment #20
czaku CreditAttribution: czaku commentedanybody any idea how to replace tt() function in D7 to get localized term name having its id?
Comment #21
davemybes CreditAttribution: davemybes commentedIn Drupal 7, if you're using Entity Translation (rather than just Content Translation), you'll have to be using the Title module as well. That will be the only way to translate the node title correctly. Then, in your View, make sure you're using this new Title field (Content: Title / Appears in ...) as the node title, and not the default node title (Content: Title / The content title.). If you have existing views, you'll have to swap the fields out and quite possibly update your styling to work with the new field.