Entity type view should provide a context for its label

Makes sense to me. Not sure this should get test coverage, looks good.

@eiriksm, sounds like a good idea.
Here's some high-level feedback from a perspective of computational linguistics and machine translation (MT):
You're correct that's a common problem, in fact much more common than most people realize. It often is discussed under "word-sense disambiguation", "lexical ambiguity" or "polysemy" (see ACL or Wikipedia). You'll see most MT systems have problems with this. To solve this, systems look at contexts (words, domains, etc.). Problems often seen:

• When targeting one phenomenon, it's often hard to visualize all the other possibilities that your solution to the phenomenon might overgeneralize (get too much) or miss (get too little)
• When specifying a list of contexts, it can be hard to split contexts up (overlap) or id all of them
• Language is so varied and unpredictable, there might still be ambiguity in the context specified

So, maybe more info than you need, but I think you're on the right track in setting something up that looks at context for appropriate translations.

function views_token_info() {
  $info['types']['view'] = array(
    'name' => t('View'),
    'description' => t('Tokens related to views.'),
    'needs-data' => 'view',
  );

I think we need to add the same context here.

Looks good to me :)

Committed 554034a and pushed to 8.0.x. Thanks!

Thanks!