Multilingual support

Hi there,

I’m wondering if there currently is any way to define language-specific values for the descriptive elements in the specification, such as description, or example?

For example:

{
  "title": "Sample Pet Store App",
  "description": "This is a sample server for a pet store.",
  "version": "1.0.1"
}

Might be rewritten to:

{
  "title": "Sample Pet Store App",
  "description": {
    "*": "This is a sample server for a pet store.",
    "fr": "Ceci est un exemple de serveur pour une animalerie.",
  },
  "version": "1.0.1"
}

Where title is a string, so it will be used as the text for all languages, while description is an object consisting of language codes that code generators can use for additional language options (in this example, the * is used as a default wildcard).

Does something like this exist?

[tigerinus]

Multilingual support in public documentation is almost certain required by many public policies. Maintaining multiple copies of OpenAPI YAML in different language is chaotic. It’d be a huge life saver to support multiple languages in OpenAPI.

Thanks!

[ghost]

Additional previous discussion: #274. Localization, internationalization or multilingual support, whatever you call it, is a must for products aiming to document something. Overlays may be overkill, and something better integrated with the specification is probably better.

It might be enough to support what was suggested in the original post: anywhere a string is supported, support an object where the keys are the language code, and the values are the translation.