Closed demirdegerli closed 1 year ago
I've disabled a Weblate localization for a reason – as I plan to rewrite the client and release it under new detached branch/repository, I discourage the users to localize my client anymore – their work will be archived sooner or later anyway. But now thinking of it, I might actually open Weblate, yet place a warning that WebCord is somewhat at going to be deprecated soon state and it is still alive as there's no alternative to it made by me.
You can use the translations as is in the new client.
You can use the translations as is in the new client.
The code structure will drastically change – it will be split into subprojects and each will have its own localization files. There will be also new concepts about translation inspired on Java/Android software design – like plurals.
This is why I most likely won't keep localization files as they are.
@demirdegerli As I'm slowly defrosting WebCord anyway, I might still consider accepting PRs and actually merge this PR after I deal with the mess left in Weblate (e.g. merge conflicts, proper warning that someone's work might be archived after I'll fully work on another client).
I'll reopen this and merge, unless you feel like against doing it.
ok
If i missed something, please let me know.