Internationalization
See original GitHub issueFor Swagger.Next we need to add i18n to description
fields. We can have two forms of description
. It can be a string or an object that has a pair of key,value for each locale/language. We can use ISO 639-2 standard (for example eng for English)
For example:
description:
eng: A simple API
esp: Un simple API
chi: 一个简单的API
Issue Analytics
- State:
- Created 9 years ago
- Reactions:9
- Comments:21 (7 by maintainers)
Top Results From Across the Web
Internationalization: Definition, Examples, and Benefits
Internationalization describes the process of designing products to meet the needs of users in many countries or designing them so they can be...
Read more >Internationalization - Wikipedia
In economics, internationalization or internationalisation is the process of increasing involvement of enterprises in international markets, although there ...
Read more >Internationalization - W3C
If you internationalize, you design or develop your content, application, specification, and so on, in a way that ensures it will work well...
Read more >Internationalization - National Communication Association |
Internationalization is about taking the rest of the world seriously, not only one's home country, and can be thought of as the formal...
Read more >Localization, Globalization, Internationalization: What's the ...
Internationalization is a corporate strategy that involves making products and services as adaptable as possible, so they can easily enter ...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
@webron #639 and #70 Seems to be about content language that an API returns. This is about the documentation language. I still looking forward to see swagger in other languages 😉
We’re looking into introducing the concept of Overlays to the spec. Overlays would allow to modify existing content and/or add to it. If this is approved, it would allow users to create language overlays that can be used to modify existing descriptions.