|
|
|
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
|
|
|
|
|
|
|
|
Tips and instructions for each of the documents:
|
|
|
|
|
|
|
|
== [https://www.transifex.com/otf/torproject/2-bridgedb-bridgedb-pot/ 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.
|
|
|
|
|
|
|
|
|
|
|
|
=== [https://www.transifex.com/otf/tor-project-support-community-portal/tpo-contentspot/ Tor Project website]
|
|
|
|
|
|
|
|
This resource translates the main [website](https://torproject.org).
|
|
|
|
You can see a preview at https://lektor-staging.torproject.org/tpo/translations/ with more languages that are being translated.
|
|
|
|
|
|
|
|
|
|
|
|
# Markdown text
|
|
|
|
|
|
|
|
### Links
|
|
|
|
|
|
|
|
One of the most common translation mistakes are the links.
|
|
|
|
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 circumvention](/circumvention)`, or `See our [documentation about circumvention](https://tb-manual.torproject.org/circumvention/)`
|
|
|
|
|
|
|
|
Remember **not to leave any spaces between [] and ()**, because otherwise the link will not work.
|
|
|
|
|
|
|
|
| good | bad |
|
|
|
|
| ------ | ------ |
|
|
|
|
| `See [here](/circumvention)` | ~~`See [here] (/ circumvention)`~~ |
|
|
|
|
|
|
|
|
## 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.
|
|
|
|
|
|
|
|
[[Image(link_to_string_in_context.png)]]
|
|
|
|
|
|
|
|
== 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:
|
|
|
|
[https://www.transifex.com/otf/tor-project-support-community-portal/translate/#it/$/154589216?q=tags%3Alocalize_link 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.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
## How to submit comments on source (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.
|
|
|
|
|
|
|
|
## Corrections to 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 here:
|
|
|
|
|
|
|
|
## 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 are confident with your changes, create a fork of our repository and submit a pull request. The changes will eventually be reflected on transifex. |
|
|
|
\ No newline at end of file |