i18nstrings module introduces a 'refresh' op to hook_locale, through which existing strings in a given group can be read in en masse. This is useful if e.g. a user enables an i18nstrings-based module when there are existing data. The refresh functionality will process these data.
For views, we'd need to iterate through all existing views and process them.
Comments
Comment #1
catchSubscribing.
Comment #2
nedjoTo explain a bit more:
i18nstrings module introduces a 'refresh' op to hook_locale, through which existing strings in a given group can be read in en masse. This is useful if e.g. a user enables an i18nstrings-based module when there are existing data. The refresh functionality will process these data.
For views, we'd need to iterate through all existing views and process them.
Comment #3
nedjoLooking at ways to add localization directly to Views, which could make this issue unneeded.
Comment #4
jose reyero commentedThis is already done. Also moved to new project. See #788290: Fix views compatibility issues (2.x, 3.x), spin off i18nviews module?