"add Case" link under Operations in project view is not translatable [#653180]

I am using the patch in http://drupal.org/node/128228#comment-2298184 and everything is working fine, except for that little thing.

Comment	File	Size	Author
#2	screenshot_cases.png	49.68 KB	castawaybcn

Support from Acquia helps fund testing for Drupal Acquia logo

Comments

Comment #1

jackread CreditAttribution: jackread commented 18 February 2010 at 20:11

This is because it is using the content type title...

If your going to rename case to something else (task?) then just change the title of that content type.

Comment #2

castawaybcn CreditAttribution: castawaybcn commented 20 February 2010 at 13:10

File	Size
screenshot_cases.png	49.68 KB

Well, I may be wrong but in the attached screenshot you can se the case is properly translated in the left menu ("add content>case" and "case tracker") but not "add case" in the project's available operations.
Please let me know what you think.

Comment #3

Grayside CreditAttribution: Grayside commented 2 March 2010 at 18:42

The name of the content type is only changed in strings generated by Drupal's node system.

That string is not, which means it needs to be separately and specifically translated.

I believe you are looking for msgid "add !name"

Comment #4

castawaybcn CreditAttribution: castawaybcn commented 3 March 2010 at 19:19

almost there Grayside!
you are right, the string is "add !name" once searched for and translated just the "add" honours the translation though. However the content type name "Case" (which I do have translated) still shows up in English.
Any ideas what I may be doing wrong?

Thanks a lot.

Comment #5

Grayside CreditAttribution: Grayside commented 10 March 2010 at 17:54

Hm, that exhausts my knowledge of the localization system.

However, if string overrides work for you as they work for me:
Try going to the bottom of your settings.php file to the string overrides. Set 'add Case' => 'add Task' (etc).

Comment #6

apaderno

he/him

Italian

Brescia, 🇮🇹 🇪🇺

CreditAttribution: apaderno commented 21 May 2010 at 21:19

The word Case is not translated because it's not part of the string to translate (which is add !name). It would be translatable if the module would use the string add case; in that case, the string to translate would be completely visible in the translation template, and translator people could translate it.

The alternative is that the module uses t('case') as value for the placeholder !name. The con in this case is that the translator people would have to translate a single word without having any context. This would make hard to translate the string in some languages where a single word can have different meanings.