>>> [!note] Migrated issue <!-- Drupal.org comment --> <!-- Migrated from issue #641128. --> Reported by: [dagmar](https://www.drupal.org/user/154086) >>> <p>I'm writing this general issue to group all related topics related to views and internationalization.</p> <p>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.</p> <p>This means that labels for tables, exposed filters, header or footers can be translated before the view is built. See <span class="drupalorg-gitlab-issue-link project-issue-status-info project-issue-status-7"><a href="https://www.drupal.org/project/views/issues/357529" title="Status: Closed (fixed)">#357529: Implement translation of customized 'translatable' views properties</a></span></p> <p>This patch should also fix this issue: <span class="drupalorg-gitlab-issue-link project-issue-status-info project-issue-status-7"><a href="https://www.drupal.org/project/i18n/issues/301020" title="Status: Closed (fixed)">#301020: Views internationalization : translation of views title</a></span></p> <p>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 <span class="drupalorg-gitlab-issue-link drupalorg-gitlab-link-wrapper"><a href="https://git.drupalcode.org/project/i18nviews/-/work_items/337348" class="drupalorg-gitlab-link">https://git.drupalcode.org/project/i18nviews/-/work_items/337348</a></span>. This kind of exposed filters needs to be processed in an special way since they don't use t() to translate strings.</p> <p>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:</p> <pre>This is &lt;div&gt;my header&lt;/div&gt;</pre><p>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 <span class="drupalorg-gitlab-issue-link project-issue-status-info project-issue-status-7"><a href="https://www.drupal.org/project/views/issues/510284" title="Status: Closed (fixed)">#510284: Header/footer/empty text and more areas pluggable</a></span></p> <p>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 <span class="drupalorg-gitlab-issue-link project-issue-status-info project-issue-status-3"><a href="https://www.drupal.org/project/views/issues/555546" title="Status: Closed (duplicate)">#555546: Translation of "Rewrite the output of this field" ?</a></span></p> <p>Finally this issue <span class="drupalorg-gitlab-issue-link drupalorg-gitlab-link-wrapper"><a href="https://git.drupalcode.org/project/i18nviews/-/work_items/324240" class="drupalorg-gitlab-link">https://git.drupalcode.org/project/i18nviews/-/work_items/324240</a></span> may 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.</p> <p>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.</p> <p>Sorry for my english but, this is about internationalization ins't? :)</p>