At least the header, footer and empty texts support filter formats.

To avoid possible (code) injection by translaters - they might contain php code - they don't trigger any translateability.

This is the reason why i18n added filter format support to the translation API.
To support those elements for clean translation, views could add filter format support for the translation layer on a per-key basis.

The filter based elements would then need to be additionally announced and translation layer called.

#2 1031962-filter_format-export.patch1.71 KBdawehner
Members fund testing for the Drupal project. Drupal Association Learn more


slashrsm’s picture

Assigned: Unassigned » merlinofchaos
dawehner’s picture

Just a general start of work.

miro_dietiker’s picture

Referring to issue that introduced header/footer pluggability.
#510284: Header/footer/empty text and more areas pluggable

MustangGB’s picture

Issue summary: View changes
Status: Active » Closed (won't fix)