Comment 5 for bug 1334382

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.