-
Notifications
You must be signed in to change notification settings - Fork 1.8k
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
Providing a Translation Environment. #2940
Comments
Yes, this is super necessary! It is much more convenient to work on a special website and be able to comment and suggest line translations, because at the moment, translating such a large project through Github is turning into a complete nightmare... I think this will also help move all these discussions and issues to a more convenient and designated place. |
I second this! A project this big that offers this many languages MUST have a translation environment. |
Yes, it would be great if translations for all localizations of Bluesky were managed on something like Crowdin. In the meantime, some language teams have set up their own projects on Crowdin. They do their translation work there and then open a PR here on GitHub when they're ready. I know that at least the Indonesian translators and the Ukrainian translators do this. |
Yes, I definitely saw it. And this only suggests that there should be a single project for translation on such a site. For example, I could help with improving the translation into both Russian and Ukrainian. Like many other users. |
Absolutely! I've been thinking about updating the Spanish localization for some time now but it not having a translation environment has put me off doing it. Having one would not only make contributing accessible to me, but also to many others. |
When I spoke about this at X, the CEO responded, which I'll include here. he said that people might think he was there for sales. Post (Japanese text) |
@mozzius @estrattonbailey @haileyok @pfrazee |
Hello Bluesky team and community. Just wanted to say that the Crowdin team would be super happy to see Bluesky on Crowdin. We will do our best to help you set up and manage the crowd localisation initiative. |
Bluesky's support responded by asking me to post on the discussion so I did. |
A hopeful update on this: @/pfrazee has said that he's hoping to get Crowdin set up sometime soon 🤞
|
Just chiming in to say that I would welcome the addition of Crowdin: it would make our work a lot easier! May I suggest that the current team of volunteer translators could have, if not a moderating role, at least a ‘trusted’ role on that platform? Of course, I don't want to seem too attached to the work we've already done in French with @surfdude29 for example, but it would be preferable to have the tools in place to ensure that the current glossary, typographical rules, etc. that we've taken the time and effort to follow through all current translations are followed by new contributors, including a way to recognise the role we had until now. (but even if we don't, it will be a net positive anyway 👍) |
As an alternative we are currently on: https://localazy.com/p/bsky Localazy works fine for this type of app from what I can see. We are moving away with bleeding heart from it because our apps have approximately 50x times as many resources, for which it became cumbersome. |
This weekend i (we) set up a project at Crowdin to translate Bluesky to interlingua (Following suggestions from another language request issues, we enabled a Crowdin project to translate Bluesky) (lang code:ia) Unfortunately for us, Crowdin has the disadvantage to not to have interlingua as an officially supported language, unlike another conlangs or fictional languages like LOLCAT or Pirate English. Some PMs refused to include our language to their projects (i.e. LineageOS) because they do not know how to create a custom language or defined to accept only official languages. |
Is your feature request related to a problem? Please describe.
Provision of a translation environment using Crowdin or Weblate.
Describe the solution you'd like
Provision of Crowdin or Weblate translation environment.
Describe alternatives you've considered
Additional context
The text was updated successfully, but these errors were encountered: