Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Define API for written translation packs #5

Open
BenHenning opened this issue Oct 15, 2021 · 1 comment
Open

Define API for written translation packs #5

BenHenning opened this issue Oct 15, 2021 · 1 comment

Comments

@BenHenning
Copy link
Member

The current API being proposed by #1 doesn't properly define language compatibility, and it's expected that we will leverage translation packs for this purpose (versus expecting all structures to be fully localized to all supported client languages).

@PasunuriSrinidhi
Copy link

Here is an example API for defining written translation packs:

POST /translation_packs
{
"pack_id": "my-pack",
"language": "fr",
"translations": {
"greeting": "Bonjour",
"goodbye": "Au revoir"
}
}

This API endpoint allows users to define a translation pack with a specific ID and language. The translations are provided as a key-value pair where the key is the identifier for the translation and the value is the translated text.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

No branches or pull requests

2 participants