| Summary: | [Feature request] Weblate integration | ||
|---|---|---|---|
| Product: | [Applications] lokalize | Reporter: | Yaron Shahrabani <sh.yaron> |
| Component: | general | Assignee: | Simon Depiets <sdepiets> |
| Status: | REPORTED --- | ||
| Severity: | wishlist | CC: | as9902613, aspotashev, fin-w, karl, shafff |
| Priority: | NOR | ||
| Version First Reported In: | unspecified | ||
| Target Milestone: | --- | ||
| Platform: | Other | ||
| OS: | Other | ||
| Latest Commit: | Version Fixed/Implemented In: | ||
| Sentry Crash Report: | |||
|
Description
Yaron Shahrabani
2021-01-27 13:03:07 UTC
This would require implementing https://bugs.kde.org/show_bug.cgi?id=277868 (In reply to Finley Watson from comment #1) > This would require implementing https://bugs.kde.org/show_bug.cgi?id=277868 Hey, why do you feel that this is necessary? Poedit implements Crowdin integration, GNOME Translator implements Damned Lies and none of these use identity management. I mean that we need some way of managing and saving log in / account details. The current system is kind of bad and generic (i think it only affects the translator details in PO files etc.) so if we want to connect to Weblate API we need to save log in details or a token or something and have a way to manage that. |