WeblateOrg / WeblateOrg/weblate

Frontend plugin integration scenario

Open
#1,066 44 comments 3 reactions 0 assignees View on GitHub
Area: API enhancement Waiting for: Demand
Dominant language
Python
Stars
6.1k
Forks
1.4k
Avg merge
9h 53m
Merged PRs (30d)
395

Description

The new API could allow a scenario I'd like to propose, which is based on https://www.transifex.com/lp/transifex-live/
- [x] Authorization via configurable API key per project - #4974
- [x] Authorization via configurable API key per user
- [x] Read all translations from a component
- [x] Read all translations from a component in a specific language
- [ ] Read one translation from a component in all translated languages
- [x] Write a translation (
- [ ] Write a comment with a translation
- [ ] Write a comment with an image of the translation (could use https://experiments.hertzen.com/jsfeedback/ which uses https://github.com/niklasvh/html2canvas to create image and highlight)
- [x] Get component translation process (for status updates)
- [x] Get repository status (in case upstream branch changed)
- [x] Push changes and get response (if API key has right authorizations)

Also see what a frontend library would look like: https://github.com/transifex/transifex-live-wordpress

This would be a really big step in continuous translation, from a translator's perspective. Please let me know what you think, maybe the API already has most use cases covered?
##

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.