Since #1157294: Exportable, Field validation rules are exportable using Ctools exportables.

However, although strings, and specifically validation error messages, can be translated by Drupal, the generated features do not include any way for the Potx string extractor to get the error messages and add them to the generated PO file for the feature.

Support from Acquia helps fund testing for Drupal Acquia logo

Comments

fgm’s picture

Title: Error codes are not exported to features » Error codes are not exported to features as translatable
Status: Active » Needs review
FileSize
6.34 KB

Here is a tiny patch exporting the strings so that Potx can see them, making it easier to distribute translations for field validation rules.

g089h515r806’s picture

looks nice.

rodrigoaguilera’s picture

I re-rolled the previous patch and cleaned the logic inside field_validation_ctools_export to just add the translatables at the end and don't mess with code the formatting and indentation that ctools does.

I kept the code style fixes.

Patch attached