Weblate: Frontend plugin integration scenario

[rvanlaak]

The new API could allow a scenario I'd like to propose, which is based on https://www.transifex.com/lp/transifex-live/

• [ ] 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?

[nijel]

The API definitely doesn't have enough yet. For 2.6 only basic translation level operations will be supported, it will be extended for future releases.

[nijel]

I've added checkboxes to your list and updated with current status.

[uhlhosting]

WordPress support is a must!

[nijel]

@uhlhosting It's on our roadmap for next year. If you have any specific requirements on it, please share them here.

CC @ilocit @orangesunny

[uhlhosting]

If any beta out there would like to test. Will keep this thread updated if anything.