wiki:doc/translation/rules

Translators are, as the rest of the Tor community, bound to respect the Code of Conduct: https://gitweb.torproject.org/community/policies.git/tree/code_of_conduct.txt

How to review other people's work:

  • Remember that is hard to receive negative feedback. Be kind.
  • Be patient. We are all learning here.
  • Try to explain why some options are better than others.
  • Share resources you use for translation (dictionaries, glossaries, etc)

Tips and instructions for each of the documents:

BridgesDB

The BridgesDB is a webpage where you can get bridges to join the tor network.

  • Some of the strings have linebreaks. Just ignore them, no need to 'translate' them.

Markdown text

The links in markdown are like this: [linked word](link)

Where link can be a URL as in https://community.torproject.org/ , or an internal link as /censorship. For example: See our [documentation about censorship](/censorship)

Remember not to leave any spaces between [] and (), because otherwise the link will not work.

You can many times add your language prefix to the translated link, for example for Spanish: Lee nuestra [documentación sobre la censura](**/es**/censorship)

But don't do it if you are translating an anchor of the same page, which are the ones that start with #. In that case, check on the page to see if the anchor has been translated. For example: Lee nuestra [documentación sobre la censura](#censura) for Spanish.

How to submit comments on source strings (English strings)

If you have comments on source strings it is always better to submit the main content repositories, as developers often don't look to the issues in transifex.

Some other documents, as the Code of Conduct, are not available for source string editions at the moment, in particular the Code of conduct has been ratified by the members of the Tor Project, and changing the text here and there will need a big organizational effort. You are invited to start that process, or wait until there are new amendments to the Code of Conduct to also proposed grammar changes.

Tor Websites

For the websites based on Lektor (Tor Browser User Manual, Support Portal, Community Portal, Tor main website) you can submit corrections as explained under here. This is the preferred way to submit such feedback, as more people will be able to act on it.

How to see the strings in the websites

When on the transifex page, see in the context tab:

  1. Click on tab to find the context
  2. See URL of the page. Copy in browser and see the current content of the string.

How to edit a source string, or submit feedback about a source string

  1. Look for the string context, and open the link on the 'Ocurrence'. For example from the picture: support.torproject.org/onionservices/onionservices-2/
  2. Click on the link 'Edit this page' at the bottom of the text. You will be offered to edit the original English strings.
  3. Once you ar confident with your changes, create a fork of our repository and submit a pull request. The changes will eventually be reflected on transifex.

Quality checks on the websites

This are ways to ensure that your translations do not have problems

  • Navigate and see how your translation looks.
    • There are preview versions for the incomplete languages at https://lektor-staging.torproject.org/ [website] /translations/
    • Check specially that the links are working correctly and don't lead to a 404 error.
    • Compare with the English version to see if the images and the styling are the same.

Review tags:

localize link this tag is added when the link can be localized. For example, if it is a link to the download page, and the page is translated to your language, you can change the link to your locale.

Tor Project website

This file generates the main torproject.org website You can see a preview at https://lektor-staging.torproject.org/tpo/translations/ with more languages that are being translated.

Last modified 8 months ago Last modified on Mar 13, 2020, 11:28:30 AM

Attachments (1)

Download all attachments as: .zip