t() calls should be avoided , use $this->t() instead in Image module

Looks good to me.

Checked each file in image module and replaced ones which were missed

+++ b/core/modules/image/src/Plugin/Field/FieldType/ImageItem.php
@@ -389,7 +389,7 @@ public static function validateResolution($element, FormStateInterface $form_sta
-          $form_state->setError($element[$dimension], t('Both a height and width value must be specified in the @name field.', ['@name' => $element['#title']]));
+          $form_state->setError($element[$dimension], $this->t('Both a height and width value must be specified in the @name field.', ['@name' => $element['#title']]));

this method is static, so no t() accessible here, also in propertyDefinitions() more t() functions used

A) This patch still applies.
B) After searching - outside of the test directory, '*.inc' and *.module files there are no calls to t()
C) After a visual scan of the patch ... all changes are of the expected form
D) There are no unrelated changes.

E)
In other issues, of a similar form, but with a small number of changes I have recommended that we stop using t() within tests
as all tests are conducted in English unless directly testing string translation.

https://www.drupal.org/project/drupal/issues/3116080#comment-13481391

This is a large enough patch .. and the number of changes to tests is significant. Additionally progress on the meta issue has slowed.

So I am not going to recommend that here.

In short RTBC.

Thanks for working on this.

In general, issues should not be scoped by file or module; instead, they should be scoped by making the exact specific change across as much of core as possible. Reference: https://www.drupal.org/core/scope#files

In particular, t() calls should be replaced based on whether the translation service is already available in the class, and more specifically, based on which base class it extends. (So, for example, one issue for form builders, one for controllers, one for list builders, and then splitting that up further only if the resulting patch is too large to be manageable.) We also need to decide the approach before we proceed with child issues. See #3113904: [META] Replace t() calls inside of classes for more discussion. So, closing as a duplicate of the parent issue in #3113904: [META] Replace t() calls inside of classes .

Thanks!