Nextcloud is available in many languages. How is that done?
Instead of maintaining our own translation server, like Pootle, Nextcloud uses Transifex to facilitate translations for many languages.
Transifex offers free service for open source projects.
Are you interested in translating Nextcloud?
Create an account on Transifex, then apply to join the Nextcloud organization. You are welcome.
Once you have joined the organization, apply to join one of the over 70 target languages available. Should yours be missing, feel free to request it.
Best way is to start translating some strings. Get an overview of what and how things have already been translated.
There are some features and functions in Transifex, but the basics is pretty much all that works.
If translating is not your boat of wood, or similar, you can be a reviewer. Even more fun
How to discuss at Transifex?
You can discuss for each string. Whoever reads it can respond. There is no way to subscribe to any discussion as long as somebody doesn’t mark the discussion as an issue.
For language teams there is a chance to discuss as well. It is not easy to find through the web UI and not many people respond (German team experience with more than 100 members)
You can send private message to other members. Inbox and outbox are separate and there is no option to see threaded messages. You cannot invite a third person to private discussions.
Using the forum is a much better idea.
Different roles at Transifex?
To understand roles and their respective permissions see https://docs.transifex.com/teams/understanding-user-roles/
You have Maintainers,language coordinators, reviewers and most importantly: translators. You are the engine of the car.
Information for Translators
Basic knowledge to start
You have joined a language team. Do not hesitate to contact people in it.
Newbie information: Whenever translating parts of a single resource please do not just translate a single string without looking at already translated strings. Most resources have a common wording and you should follow it. If you have a different position you should discuss first before changing strings.
Translate easy ones before trying complex ones.
Do not use translate.google.com to just enter and copy result to Transifex.
Whenever you need triple dots (punctuation mark) to show progress or similar status you should use unicode character ‘…’ instead of html entity (… ; … ; &hellip e.g. ‘Uploading …’
- No space before ellipsis if you shorten a word
- Space before ellipsis when you shorten a sentence
When to comment a string at Transifex?
If you are struggling to translate a string feel free to add a comment including your question.
You like to discuss your thoughts? No problem, just invite your team members using @username.
When to create an issue at Transifex?
Whenever you feel just a comment is not sufficient and you need information to help all other language translators feel free to mark your comment as an issue.
What to do if I want to change a source string?
Sometimes you encounter a typo or some other spelling error inside a source string. Or you find an error or grammar issue. If so, feel free to file an issue by marking a comment as an issue, or, even better, go to GitHub and provide a PR (Pull request) to correct it.
Most translators are not familiar with coding tools like GitHub nor have any coding background. It is though easy enough to make a GitHub account and navigate to the related repository. From there you can file issues directly where coders see it, get help, and learn to fix things on your own. GitHub has a bigger community since it is more integrated in the workflow.
Information for Project Maintainers
How to handle new language requests?
Nextcloud wants to cover the world. To reach this target as many languages as possible need be covered.
Luckily every week we get new language requests. Great. But do not simply accept it.
Please check if similar languages are already there. If so, check the team size and send a personal message to the language requester. Tell him/her about the language you found, provide link to team and ask her/him to join named team.
How to work on issues
- In case of errors in source strings, an issue must be created at GitHub. The most difficult task is finding the right project. Be sure to check if the topic has already been reported.
- A detailed explanation should be given in case of comprehension questions.
- Don’t close an issue without an explanation. The creator deserves an answer.
- We close issues older than one year without activity.
Information for German Team Members (in German)
Moved to separate page. Link: