Field label translations overview

Overview of the field label (and description) translations of every bundle of
an entity type, one table per bundle, one column per language.

Compatible with Drupal 8.0+ up to Drupal 11 (PHP 5.5+ syntax).

Requirements

• Required: field, language.
• Optional:
  • config_translation: translation links for fields and bundles.
  • locale: translations of base fields defined in code, and the .po export.

Installation and permissions

1. Enable the module: drush en field_label_translations.
2. Grant the View field label translations overview permission
   (view field label translations) to the roles that need it.

Translation links are shown only if the user has access to the target page,
e.g. with the Translate configuration or Translate interface text
permissions.

Usage

Open Configuration > Regional and language > Field label translations, or go
to the URL directly:

/admin/config/regional/field-label-translations/{entity_type_id}

defaults to node. Any fieldable entity type works, e.g.
taxonomy_term, user, media. Use the filter at the top to
switch entity type, or to show the base fields defined in code too
(?base_fields=1).

The tables

• The first row is the bundle label and its translations.
• The other rows are the fields, identified by their machine name in the first
  column, and their type below it.
• Each language cell shows the label, with the description below it.

Markers:

Marker Meaning original (yellow) The source language of the label. missing (red) No translation on this language. description missing The label is translated, but the description is not. untranslatable (grey) The label can't be translated, e.g. the config's source language is und/zxx, or the bundle has no bundle entity. Orange row Base field, or base field override.

Hover links, which open in a new tab:

• First column: All translations opens the core Translate tab of the
  field or bundle. It isn't shown for base fields defined in code.
• Language cells: Add translation, Edit translation or
  Edit original. For base fields defined in code, Translate interface
  string opens the interface translation page filtered to that string and
  language.

Base field overrides (e.g. a base field label changed on a bundle) are config.
They don't inherit the interface translations of the base field, and core has
no translation UI for them, so they have no links.

Exporting base field translations (.po)

The Export base field translations (.po) section at the bottom of the page
exports the labels and descriptions of the code-defined fields of the entity
type. It requires the locale module.

1. Select the target language.
2. Check Include already translated strings to export every string. Leave it
   unchecked to export only the strings without a translation in that
   language.
3. Click Export. You get {entity_type_id}-base-fields.{langcode}.po.
4. Translate the file, then import it at Configuration > Regional and
   language > User interface translation > Import.