"Translation update status" in locale.install is not translated

Right so related projects are:

Drupal core: 8.0-alpha2 (4), 8.0-alpha3 (4), 8.0-alpha4 (4), 8.0-alpha8 (4), 8.0-alpha7 (4), 8.0-alpha6 (4), 8.0-alpha5 (4), 8.0-alpha9 (4), 8.0-alpha10 (4), 8.0-alpha11 (4), 8.0-alpha12 (4), 8.0-alpha13 (4), 8.0.0-alpha14 (4), 8.0.0-alpha15 (4), 8.0.0-beta1 (4), 8.0.0-beta2 (4), 8.0.0-beta3 (4), 8.0.0-beta4 (4), 8.0.0-beta6 (4), 8.0.0-beta7 (4), 8.0.0-beta9 (4), 8.0.0-beta10 (4), 8.0.0-beta11 (4), 8.0.0-beta12 (4), 8.0.0-beta13 (4), 8.0.0-beta14 (4), 8.0.0-beta15 (4), 8.0.0-beta16 (4), 8.0.0-rc1 (4), 8.0.0-rc2 (4)

Which version of Drupal are you using?

Ok I did this:

$ git grep "Translation update status"
core/modules/locale/locale.install:              'title' => 'Translation update status',
core/modules/locale/locale.install:              'title' => 'Translation update status',
core/modules/locale/locale.install:            'title' => 'Translation update status',
core/modules/locale/locale.install:          'title' => 'Translation update status',
core/modules/locale/src/Form/TranslationStatusForm.php:   *   Translation update status as an array keyed by Project ID and langcode.
core/modules/locale/src/Form/TranslationStatusForm.php:   *   Translation update status as an array keyed by language code and
core/modules/locale/src/Tests/LocaleUpdateInterfaceTest.php:    $this->assertNoText(t('Translation update status'), 'No status message');
core/modules/locale/src/Tests/LocaleUpdateInterfaceTest.php:    $this->assertText(t('Translation update status'), 'Status message');
core/modules/locale/src/Tests/LocaleUpdateInterfaceTest.php:    $this->assertText(t('Translation update status'), 'Status message');
core/modules/locale/src/Tests/LocaleUpdateInterfaceTest.php:    $this->assertText(t('Translation update status'), 'Status message');

So as you can see only tests include this string wrapped in translation markers. Tests are not parsed for strings to avoid them littering what translators need to work on for useful translations :) If you look at locale.install, this looks like a core bug several times over:

          else {
            $requirements['locale_translation'] = array(
              'title' => 'Translation update status',
              'value' => t('Missing translations'),
              'severity' => REQUIREMENT_INFO,
              'description' => t('Missing translations for: @languages. See the <a href=":updates">Available translation updates</a> page for more information.', array('@languages' => implode(', ', $untranslated), ':updates' => \Drupal::url('locale.translate_status'))),
            );
          }
        }
        else {
          $requirements['locale_translation'] = array(
            'title' => 'Translation update status',
            'value' => t('Up to date'),
            'severity' => REQUIREMENT_OK,
          );
        }
      }
      else {
        $requirements['locale_translation'] = array(
          'title' => 'Translation update status',
          'value' => \Drupal::l(t('Can not determine status'), new Url('locale.translate_status')),
          'severity' => REQUIREMENT_WARNING,
          'description' => t('No translation status is available. See the <a href=":updates">Available translation updates</a> page for more information.', array(':updates' => \Drupal::url('locale.translate_status'))),
        );
      }

Also more than those 3 cases are in the file :)

If those strings have the same root case yes, otherwise no.

This issue is ironic.

We are also currently at version 8.2.5. (@ulfg on slack)

Created an initial patch. Please review it.

Patch looks good, thanks for the work. The title is now translated (see screenshot).

I've checked that all interface texts "Translation update status" are now wrapped in t(). All occurrences of 'title' => in locale.install now use t().

The "Translation update status" string is covered in the test script, but the tests uses English interface language (see LocaleUpdateInterfaceTest). Not sure if we need additional test coverage to prove that the string actually is translated.

We can't have test coverage of every single translatable string, while I can see us adding test coverage for complex cases, this is a pretty trivial oversight, so I'd say RTBC :)

Setting back to RTBC

crediting @Gabor Hojtsy for research/mentoring/guidance on how to resolve this.

Committed as 412c756 and pushed to 8.5.x - thanks