Skip to content

Internationalization (i18n) / multilingualism for some text fields ? #86

@LaurentAjdnik

Description

@LaurentAjdnik

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!

Metadata

Metadata

Assignees

No one assigned

    Labels

    enhancementNew feature or request

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions