API endpoint service names are not translated

[Doug Fish]

On the Project->Compute->Access & Security->API Access tab the Service column data is not translated.

[Ashish Chandra (ashish-chandra)]

I Agree with you Doug. The naming of entries in Service Column should be:

Volumev2 -- > Volume v2
Computev3 -- > Compute v3
Cloudformation --> Cloud Formation

[Ashish Chandra (ashish-chandra)]

AFAIK, the fields are populated from an API call from Keystone and we put in the same name as it is mentioned in keystone service list with first letter capitalised.

[Amit Prakash Pandey (amitpp23)]

same problem in Admin --> System --> System Info --> Services -> Name and Service columns too.

[Doug Fish (drfish)]

I think Ashish made a good point: the data we are showing in Horizon comes directly out of the API call. It seems that if we are going to translate that data the translation should come through the API so that the CLI and any other API client can show the tranlated information.

The API we are discussing corresponds to the
keystone service-list

[Morgan Fainberg (mdrnstm)]

So the issue here is how do you propose to get the i18n information? The service names are not "static" and can be named whatever is desired by the deployer. This is not something that is easy to guess about, since we can't know every name that a deployer wants to use.

I honestly don't think it's possible to do normal i18n work on this front. This is most certainly not something keystoneclient can solve. While I'm open to suggestions, I am skeptical that this is something we can really tackle since it's deployer defined strings.

I'm going to say (at the least) for client this is invalid and warrants a different conversation about handling this in a smart way if at all. The data cannot come from transifex/the-new-tool-that-starts-with-a-Z if it's up to the deployer to name the service.

[Dolph Mathews (dolph)]

Those also look like service *types*, which are standardized, case-sensitive strings that should not be arbitrarily capitalized nor translated. Service *names* are user defined, and if a deployer wants to use translated strings there, they can do whatever they want (including branding, etc).

[Doug Fish (drfish)]

Morgan, Dolph thanks for your feedback on this. I did not realize that these were deployer selected values. I understand why they cannot be translated. It would be a mistake to try to translate these in Horizon for the same reason.

Dolph, just to be sure there isn't some capability I'm not aware of, when you say "if a deployer wants to use translated strings there", you mean that a deployer can provide a non-english string that would always be presented right? We don't have any mechanism where the deployer could provide an English word like "compute" and a set of translations for compute and have a translated description shown, right?