Cannot translate operations / missing in translatables

This module just provides default views, this would be exported from the vbo integration, and we are not in the game of manually adding translations to view exports.

This is not an issue for admin views.

None of those strings are in Views. Why is that here?

Views generally adds a list of translatable strings to all view exports, unless you actually turn that feature off. So maybe the views need to be re-exported with the strings. But that's not Views' job.

We are talking about bulk operation options only here, if anything this should be in vbo. It's not a views or admin views problem IMO.

How can this be solely an admin views bug? You will see this any time you use vbo.

It's a bug in views bulk operations, that these strings, which are entered in the views UI, aren't marked as translatable through option_definition().

Once this is fixed properly in VBO, someone can rexport the views in admin_views and then you will have the strings on there.

If I understand the original report correctly, the operation names are untranslatable.

However, I was able to translate the operation names using the latest VBO 7.x-3.x-dev, including "Stick", like this:
* Enable locale.module
* Enable admin_views.module
* Enable an additional language and navigate to admin/content in that other language
=> The operation "Stick" appears in English
* Open a separate browser tab at admin/config/regional/translate/translate
* Filter the strings on "Stick"
* Translate the relevant string
* Refresh first tab
=> The operation "Stick" appears in the other language

Does this procedure fail for you? If so, where?

Thanks for the info. I committed a fix to VBO to add custom operation labels to the translatables.

What's needed now is to generate a patch for Administration Views, with the admin views containing the updated translatables.

+          'value' => t($operation['label']),

I don't think we want to have the label translated in the actual export.

@dawehner, that's how other translatables work. I checked by exporting a view while in another language: I got the localized strings on all translatables.

Yes, I am just being consistent with the rest of Views.

Although the fact that strings are surrounded by t() in the exported code is different from the fact that they are themselves localized during export.

@hass, any news from your testing? There's no point in keeping this issue open on the VBO side - I've done what needs to be done here.

After spending an hour tracing through Views code, it appears that the option strings are *already translated* when they reach the translation export functions. I think the Views core translation export should be getting its strings from an untranslated source instead - this needs more work.

Since there's an open issue for that, I've removed the t() call from the operation labels. Committed the fix.

It would be great to move this issue to the next step.