Add more API languages.
See original GitHub issueHey, love this repo!
I play DnD in Ukraine, and we use Russian as our primary language for the parties, so I would love to have this API available in different languages.
Maybe creating folders like en
, ru
and just storing the different json
files there would be a good option?
I am ready to contribute, just don’t want to deploy my own API 😃
Issue Analytics
- State:
- Created 4 years ago
- Comments:35 (2 by maintainers)
Top Results From Across the Web
Building a multilingual RESTful API | by Guillaume Viguier-Just
Representing a resource in multiple languages · Option 1 : use language as an object attribute · Option 2: add language as another...
Read more >Making Win32 APIs More Accessible to More Languages
Making Win32 APIs more accessible to more languages will allow developers to make the most out of Windows regardless of their preferred language...
Read more >Language Extensions Overview - Visual Studio Code
Learn how to write a Language Extension (plug-in) to add support for a programming language in Visual Studio Code.
Read more >Add a Language - Contentstack
Go to your stack, click the “Settings” icon (press “S”) on the left navigation panel, and select Languages (or press “alt + L”...
Read more >Adding content in multiple languages - IBM
You can provide custom pages in multiple languages to your APIs and Products to improve your customer experience and understanding.
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
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
This could work, indeed. But that’d require a lot of work to do the mapping which I don’t know how to do. @bagelbits any insight on how to do so?
However I wouldn’t go as far as to include the country so far (enUS, esES), because there are simply not enough translations yet. Also I don’t like the file naming: usually, in the programming languages I know, different locales are named as
_<language>
or_<language>_<country>
, where<language>
is the 2-characters ISO 639-1 representation of a language and<country>
would be the 2-characters ISO 3166-1 representation of a country.So basically, I’d recommend using:
Does the SRD exist in any other languages currently? There is prob a risk of copyright infringement as well, validating that translations are not pulling from proprietary (D&D) info. Just pointing that out as something to think about.