Change dropbutton labels on translations tab to "add translation" / "edit translation" / "delete translation"?

'delete' also should be changed to 'delete translation'.

Changed 'delete' label to 'delete translation'.

a link to the translations tab could already be displayed on the main content overview drop down.

this would probably introduce a hook in entity_translation, did not find it till now - too much time spent already ..
(tried translation_entity_node_operations > this is for bulk ops, and translation_entity_menu_local_tasks_alter > this is for the blue links on top .. )

#6: 1831604-et-dropbutton-labels-6.patch queued for re-testing.

Needs screenshot

i would like the link to the translations here too :D

@Bojhan here it is.

Yeah, hm, as with the phone call where we discussed this I'm not sure that this is an improvement per say. You *are* on the translation page. I mean on the views screen or the node admin page, the links do not say "edit view" or "edit post", they just say edit, because the context makes the action evident. This looks very un-Drupal AFAIS. Essentially too verbose. However, this is just IMHO, so if people feel this is an improvement nonetheless, I have no intention to stop it :D

I am pretty sure its not really an improvement, so I would just won't fix this.

You are in the language flow, the buttons don't necessarily need to signal that. And doing so actually makes it a lot harder to scan, than without.

Right, ok, we agree then. Thanks for the work guys, don't give up just yet :)

actually, i don't see the textual change as an improvment, but #11 would be - at least for me .., saving a click.

@ytsurk: Yes, I think an issue for that would be great to have. :) Not to overload this one. Same applies for taxonomy terms, etc. I'd have loved to have that quick access as well as I tried it out.... Can you open a new issue?

I updated the issue summary

If/when someone creates an issue for #11, please link it in here :)

Well, created this one: #1832778: Include translation operation in overviews for translatable entities. Anybody want to look into working on it? :) I think the hard part about it will be that you need to check per entity on each row. The set of operations will possibly be different for different nodes based on whether they are translatable or not (have a base language, node type configured to be translatable, etc). Same for taxonomy terms, etc. I think the visibility/access rules for the menu tab would need to be applied essentially.

(Posting same on that issue).

Issue summary updated.

Updated issue summary with the link to the follow-up issue