Closed (fixed)
Project:
Internationalization
Version:
6.x-1.0-beta3
Component:
Compatibility
Priority:
Normal
Category:
Feature request
Assigned:
Unassigned
Issue tags:
Reporter:
Created:
14 Aug 2008 at 13:55 UTC
Updated:
21 Dec 2012 at 17:01 UTC
Jump to comment: Most recent file
Comments
Comment #1
jose reyero commentedViews integration/translation is WIP, see http://drupal.org/node/313262
Comment #2
Anonymous (not verified) commentedAutomatically closed -- issue fixed for two weeks with no activity.
Comment #3
Alice Heaton commentedI'm re-opening this, as I have a patch to offer for this feature. It's implemented as a form_alter hook in i18views.
Patch from the root of i18nviews.
Comment #4
jose reyero commentedThe patch looks good.
Any reason why we shouldn't be using the field id as the string key?
Comment #5
jose reyero commentedThere's a complete solution for views here, #360024: Write views localization plugin
So I'll be committing that one if the related patch gets into Views. Otherwise we'll go for this one as a temporary solution.
Comment #6
joostvdl commentedI created a patch for the plugin based in the patch form #3. You can find it at #360024: Write views localization plugin
Comment #7
boobaasubscribe
Comment #8
jose reyero commentedThis should be fixed with #360024: Write views localization plugin
But needs this views patch: #357529: Implement translation of customized 'translatable' views properties
Please follow up here: #641128: [meta] Internationalization tasks for views 3
Comment #9
jose reyero commentedModule moved to new package. We have now two branches (views 2.x / 3.x)
Comment #10
cesabal commentedBe careful with function tt() this function is deprecated, use i18n_string() function