I started only for fixing t('!action by @user.' bug, but after a few minutes I decided to make a full review, what ended with a lot of strings that need changes.

Comments

Status: Needs review » Needs work

The last submitted patch, Workbench_Moderation_Translatable+string+review_20120901.patch, failed testing.

hass’s picture

Status: Needs work » Needs review
StatusFileSize
new25.16 KB

New try... too many brackets... :-)

hass’s picture

Still applies.

hass’s picture

Issue tags: +Workbench Sprint
kbentham’s picture

Status: Needs review » Reviewed & tested by the community

This patch looks good.

stevector’s picture

There are a bunch of in-progress patches that edit the exported view like #1781744: Draft and Needs review pages are broken

I'd rather patch that View only once so we're not stuck rerolling too many patches. hass, what do you think of committing this patch minus the changes to the View?

hass’s picture

Last weekend I have applied http://drupal.org/node/1781744#comment-6932118 first and than this patch without any hunks. Other commit orders have not tested by me. If it's only the view, we can re-role.

hass’s picture

hass’s picture

+++ b/workbench_moderation.node.inc
@@ -182,7 +182,7 @@
-      $row['data']['moderation'] .= '<div class="moderation-actions">' . t('Moderate') . ': ' . drupal_render($moderate_form) . '</div>';
+      $row['data']['moderation'] .= '<div class="moderation-actions">' . t('Set moderation state: !moderation-actions-form', array('!moderation-actions-form' => drupal_render($moderate_form))) . '</div>';

In #1548050: Change t('Moderate') to t('Set moderation state') has a conflict with this patch. It's a better fix in #1548050: Change t('Moderate') to t('Set moderation state') than here. Many months between both patches... the one hunk can just be ignored.

hass’s picture

Re-roled patch because of hunks.

stevector’s picture

Status: Reviewed & tested by the community » Fixed
hass’s picture

Are these strings used in 2.x and are we running in regressions here?

Automatically closed -- issue fixed for 2 weeks with no activity.