Hello.
All text fields included in the spec are provided on a single-language basis.
As often, English is the most widely used language, in the spec or examples found elsewhere.
It is usually not a problem when dealing with APIs, since these are seen only by developers or machines.
However, with MCP, I understand some texts (prompts, descriptions...) might be read / selected / typed directly by end users.
Are there any plans to provide an internationalization (i18n) / multilingualism mechanism in the spec?
Or shall we rely on the LLM to handle the (possibly not totally accurate) translations?
Thanks!
Hello.
All text fields included in the spec are provided on a single-language basis.
As often, English is the most widely used language, in the spec or examples found elsewhere.
It is usually not a problem when dealing with APIs, since these are seen only by developers or machines.
However, with MCP, I understand some texts (prompts, descriptions...) might be read / selected / typed directly by end users.
Are there any plans to provide an internationalization (i18n) / multilingualism mechanism in the spec?
Or shall we rely on the LLM to handle the (possibly not totally accurate) translations?
Thanks!