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

Translation workflow #411

Open
rffontenelle opened this issue Aug 2, 2021 · 2 comments
Open

Translation workflow #411

rffontenelle opened this issue Aug 2, 2021 · 2 comments

Comments

@rffontenelle
Copy link
Contributor

appstream-glib project in Transifex is no more, but I see that you had second doubts about it. Still, the README.md has instructions to use Transifex.

It seems this should be solved by removing Transifex mentions and use pull requests, or setting up in a translation platform (personally I would go with Weblate, or Fedora Weblate as suggested by Jean-Baptiste in #339).

@hughsie
Copy link
Owner

hughsie commented Aug 3, 2021

The problem I had/have with zanata/weblate is that it's perceived as Fedora specific. Transifex might be closed source, but it's open to all and neutral. That said, it's not entirely obvious how I add appstream-glib back to the freedesktop transifex organisation....

@rffontenelle
Copy link
Contributor Author

So, the team manager role in freedesktop organization doesn't give you permission to add projects, right? I don't have any Transifex-related suggestion other than you create a separate project in your own organization in Transifex.

Regarding Weblate, you could use Hosted Weblate as it is gratis for free/libre software (instead of Fedora Weblate instance). Steps start with creating an account, requesting a project for libre software and make it available for people to contribute.

Alternatively, instead of creating a project, there is the AppStream project in Weblate, in case you want to "join forces" with ximion to make two translation components (appstream and appstream-glib) under a single project and use a common glossary to keep consistency between them.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants