Wp-calypso: Purchases: String 'Manage Purchase' is not localized

[gedex]

Steps to reproduce

1. Starting at URL: https://wordpress.com/purchases
2. Go to the purchased plan
3. See the title on the top, 'Manage Purchase'.
4. Switch to another interface language and verify step 3 again.
   

   What I expected

The string 'Manage Purchase' is translated to user's interface language.

What happened instead

The string 'Manage Purchase' is not translated to user's interface language.

Browser / OS version

Chrome 51.0.2704.103 (64-bit) / OSX 10.11.14

Screenshot / Video

Interface language set to 'es'.

[fabianapsimoes]

It does seem like the string is translatable (see) and that there is a translation available for es (see).

@akirk could you take a look and check if that string has been deployed already? Or maybe there's some other reason why the translation isn't showing?

[akirk]

Defining a context in this way doesn't work.

When we extract strings for translation, we are looking just at the raw js text file, we don't run JavaScript (it would be too complex). So for that reason the string gets added to GlotPress without a context (no grey box with white text next to the original) but when we ask for displaying the string, a context is provided Title text, hence no translation with that context can be found.

Two possible solutions:

• Remove the context, i.e. L6 (preferable in this case)
• add the context verbatim in each line (will require a full translation cycle: extract new string to GlotPress, send for translation next week, get string back and deploy)

[akirk]

cc @gziolo who created this code.

In general, context is like commas in English: when in doubt, leave it out. Context is only needed if it shows that the same text needs to be translated differently in two locations of our UI, depending on the _context_. I know that adding context is well-intentioned but if you want to help the translator (and that is very much appreciated!), please use a comment.