Translatable strings review

Patch does not apply.

Its good to make the descriptions better.

No updates after the needs work in more than 6 months

I see esmerel's name as a list of Views maintainers.

I do not see hass' name on the list of Views maintainers.

Please do not give us orders. If you want to reroll the patch, please do so, but issues that are 'needs work' for 6 months are still considered open and clearly nobody is doing the work.

I'd care, but since you've never lifted a finger to actually ease the burden of maintaining this issue queue, but instead have consistently added additional burden through being stubborn and combative, you should not be surprised that I don't jump up and down to review your patches.

The line endings of 3.x was changed. Please rerole a valid patch against 3.x

A valid patch means not 250 kb.

The problem with patched translations in 2.x cycle is that you might brake existing translations.

HEAD points afaik to an old 2.x version.

-      '#title' => t('Require this relationship'),
+      '#title' => t('Relationship is required'),

Changing this from an active (the checkbox does something) to a passive (the checkbox is something) is not an improvement in English.

-        '#title' => t('Force single'),
+        '#title' => t('Force single option'),
         '#description' => t('Force this exposed filter to accept only one option.'),

Space here is pretty tight, I don't see value in adding the word 'option' there. Additionally, it appears in the description. If the title of the checkbox is going to be more than a word or two,t hen we should omit the description. However, 'force single option' is not enough more descriptive than 'force single' so the description is still necessary. Therefore, I don't like this change. The same is true for all of the filter checkbox changes in the patch.

-        $errors[] = t('Style @style requires a row style but the row plugin is invalid.', array('@style' => $this->definition['title']));
+        $errors[] = t('Style %style requires a row style, but the row plugin is invalid.', array('%style' => $this->definition['title']));

While the addition of the comma is valid here, English rules say that on short clauses the writer can omit it. I would rather not make this change and break the existing translations just to add a comma. I'm not particularly against the comma, mind, but just don't see the need to change it.

-            <?php print t('Path: !path', array('!path' => $view->path)); ?> <br />
+            <?php print t('Path: @path', array('@path' => $view->path)); ?> <br />

I'm not sure why you think this is valid, but that change actually breaks the UI.

-    'help' => t('The translation status of the node--whether or not the translation needs to be updated.'),
+    'help' => t('The translation status of the node - whether or not the translation needs to be updated.'),

In English the double dash without spaces is correct and the single dash with spaces is not.

-  alert(Drupal.t("An error occurred at @path.\n\nError Description: @error", {'@path': path, '@error': error_text}));
+  alert(Drupal.t("An error occurred at path @path.\n\nError Description: @error", {'@path': path, '@error': error_text}));

I don't feel that the addition of the word path is necessary here.

-            drupal_set_message(t('@type handler @table.@field is not available.', array(
-              '@type' => $info['stitle'],
-              '@table' => $handler->table,
-              '@field' => $handler->field,
+            drupal_set_message(t('%type handler %table.%field is not available.', array(
+              '%type' => $info['stitle'],
+              '%table' => $handler->table,
+              '%field' => $handler->field,

I don't feel like use of theme('placeholder') here is valuable.

-  $form['#title'] .= t('Configure @type', array('@type' => $types[$type]['ltitle']));
+  $form['#title'] .= t('Configure %type', array('%type' => $types[$type]['ltitle']));

The use of % is definitely not right here, it's not a proper name. It's supposed to form a sentence on its own.

-  $form['#title'] .= t('Rearrange @type', array('@type' => $types[$type]['ltitle']));
+  $form['#title'] .= t('Rearrange %type', array('%type' => $types[$type]['ltitle']));

Ditto. Skipping others like it.

So this needs work :)