At the end of some .inc files generated by Features (let's consider FEATURENAME.features.field.inc), we notice that the developer took care to include some calls to the t() function so that the corresponding strings can be parsed by potx:

  // Translatables
  // Included for use with string extractors like potx.
  t('Body');
  t('Enter a comma-separated list of words to describe your content');
  t('Image');
  t('Tags');
  t('Upload an image to go with this article');

Thanks to this, it is indeed easy to create .po files containing the relevant translations. Unfortunately, I cannot figure a way to force Drupal to actually use these translations... What am I missing?

Comments

mpotter’s picture

mpotter CreditAttribution: mpotter commented
Status: Active » Closed (works as designed)

Using the normal Drupal translation pages in your site configuration.

Paul B’s picture

Paul B CreditAttribution: Paul B commented
Version: 7.x-1.0-rc2 » 7.x-1.0
Component: Documentation » Code
Category: Support request » Bug report
Issue summary: View changes
Status: Closed (works as designed) » Active

AFAIK, field labels and descriptions are not translated unless the i18n module is installed.
I don't use the 18n module so I write field descriptions in Dutch. If my fields are exported to a feature
I end up with Dutch texts in my translation interface which is messy.
Maybe the Features module could try to detect if translatables are actually translatable?

hefox’s picture

hefox CreditAttribution: hefox commented
Category: Bug report » Support request
Status: Active » Closed (works as designed)

The translatable are there so to generate .po files and such, it's standard exportable stuff, I don't think features has any plans to change this at any stage.