-
Notifications
You must be signed in to change notification settings - Fork 2k
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
Better way to handle translations #6751
Comments
You can usually check how complete each localisation is by looking at the linter output for a PR. For instance, here click on Check & compile i18n and you'll see a table like this which lists the total number of strings and the number of missing ones for each locale: However, GitHub actions are temporarily disabled at the moment due to a potential security vulnerability. On moving to a platform like Crowdin, this has been suggested quite a few times (I gave a rather long explanation here if you're interested). However, @/pfrazee said more recently that he's going to try to get Crowdin set up, so hopefully we translators won't have to wait too much longer 🤞😅 |
Also, I forgot to mention @monty241's kind offer to use Localazy: #6244 (comment) |
@surfdude29 No problem, best is to include the desired language in the access request when asking to join https://localazy.com/p/bsky so I can make sure to load any possibly existing translations. Downloading is really easy once completed:
There is also a free SQL-driver for Localazy (I work there; we needed it for our own purposes so we made a free one available), see some queries at https://forums.invantive.com/tag/localazy. |
Yea |
Great news! Bluesky is now using Crowdin! Please see #7685 for all the details. |
Describe the Feature
To be honest, it's difficult to get an overview of the translations, especially if you want to check how complete they are. A service like Crowdin could solve this and motivate more people to contribute to the translation.
Attachments
No response
Describe Alternatives
No response
Additional Context
No response
The text was updated successfully, but these errors were encountered: