I'm writing this general issue to group all related topics related to views and internationalization.
As you know, there is a patch for views 3 to translate all the string of a view. Well this is not completely true, this patch provides a new kind of plugin that allow modules to translate string when they are loaded in a view.
This means that labels for tables, exposed filters, header or footers can be translated before the view is built. See
This patch should also fix this issue:
However there another strings that need to be translated. For one side values into exposed filters needs to be translated. A filter for node types will be translated without problems, however, a exposed filter for multilanguage taxonomy terms will not be translated. There is an issue related to this topic. See. This kind of exposed filters needs to be processed in an special way since they don't use t() to translate strings.
There is also problems with Full HTML headers, footers and empty text. Since t() doesn't allow some html tags, users can't translate headers like:
This is <div>my header</div>
A possible solution for this is implementing this in a new plugin for headers footers and empty text, however Earl Miles said that he prefers a less intrusive patch. So, this can be a opportunity to implement an "Full HTML translatable Header/Footer/Empty" from i18n. See
Headers and footers are not the only places that need be processed in a special way. When a field is marked as "Rewrite the output of this field" users may need translate. See
Finally this issuemay be implemented in several way, one possibility is creating a new plugin that expends views_plugin_display_page allowing a path per language, but this is only an idea.
So, there is a lot of work to do. I wrote this issue to see if something is missing and see if finally we can get a full translatable view with views 3.
Sorry for my english but, this is about internationalization ins't? :)