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

Language translations gone #912

Closed
cek-cek opened this issue Jan 20, 2025 · 2 comments
Closed

Language translations gone #912

cek-cek opened this issue Jan 20, 2025 · 2 comments
Labels
bug Something isn't working

Comments

@cek-cek
Copy link

cek-cek commented Jan 20, 2025

Hi @MohamedBassem!

Yesterday I have completed a full Slovak translation on Weblate. To my surprise, as of today, there is no trace about the translation.

When I finished, I have noticed that there were only three languages 100% completed - Slovak, English and Korean. Seeing that Korean is now missing as well, I am pretty confident there has been some issue with merging submitted changes. There was a warning icon next to every language with hints how to resolve it by owner, but now these icons are not present anymore. Last thing I have observed yesterday was that the project got "locked", presumably when you went to resolve the issues.

Therefore I would like to ask, was this "cleanup" an intentional action or only accident? Very probably many more community submissions were lost in the process.

Is there any chance to resurrect our submissions?

Thank you.

@MohamedBassem
Copy link
Collaborator

@cek-cek It seems like something gone wrong on the weblate website, apparently they reseted the repo (due to merge conflicts) or something and the un-synced translations got wiped. I'm really really sorry this happened :(

@MohamedBassem MohamedBassem marked this as a duplicate of #928 Feb 1, 2025
@MohamedBassem MohamedBassem added the bug Something isn't working label Feb 1, 2025
@cek-cek
Copy link
Author

cek-cek commented Feb 2, 2025

Ah I see. I thought it is some common project's owner maintenance scenario that can go wrong during release. Therefore I wanted to give a heads up to refine the process in the future. And had a little hope you have a local copy of that repo locally. But if it is on them and outside your control, there's not much to improve nor revive, therefore closing this issue.

Thanks for looking into this, hopefully it was a one time bad luck :)

@cek-cek cek-cek closed this as completed Feb 2, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants