Instant Search: Non-English taxonomy filter is encoded

[gibrown]

Steps to reproduce the issue

1. Follow instructions in Instant Search: Update prototype with downstream changes #13761 to get search running
2. Configure a taxonomy filter for language on wordpress.tv
3. Load up the filters and you will see:

[bluefuton]

Is the plan to fix this encoding in the endpoint, or do we want to do it on the client side?

[gibrown]

I was thinking in the client, but I really haven't looked at exactly what is coming from the API and ES.

[jsnmoon]

I think the correct approach would be to correct this in the API.

In an ideal world, the above screenshot might look like the following:

• english should be English, or English (American)
• spanishespanol should be Spanish (Español)
• germandeutsch should be German (Deutsch)
• frenchfrancais should be French (Français)
• japanese%e6%97%a5%e6%9c%ac%e8%aa%9e should be Japanese (日本語)

[bluefuton]

Available fields: https://developer.wordpress.com/elasticsearch-post-doc-schema-v2/#es-mapping-post-tags

[jsnmoon]

Fixed in #14437.