Help documents

This describes how is translated

Translation of

Here you will find outdated information on how the translation of help documentation is handled.

What this is

Riseup’s help documentation is collected at, these help documents describe many of the most common questions that we get. These range from how to setup common mail clients, questions about spam, documents about the collective, etc.

How translation is was done

(we are in the process of moving riseup help into crabgrass, so this process is out-of-date)

  1. you must first have a riseup email account
  2. once you have a riseup email account, you will need to request ‘translator’ status for your account. To request this, you can send an email to, or fill out a help ticket
  3. go to the page you want to translate on, make sure you are visiting the https version of the page, and not http! If you visit the http page, your riseup email password will be compromised!!
  4. type “Alt-e” in firefox/mozilla or put ?edit in the url for other web browsers (for example:
  5. You will be asked for a login/password the first time you go to edit a page, use your riseup username and password, you will not be able to login here if you do not have translator status!
  6. In the lower left hand corner there is a drop-down menu, change it from English to the language that you are going to translate to. Be sure you do this before you make any edits!!
  7. Look at the top of the edit box, if there is “TRANSLATION IN PROGRESS” at the top, then someone else is working on this page right now, pick another. If it doesn’t say this, then nobody is working on it.
  8. Put “TRANSLATION IN PROGRESS” at the top and then click the “save” button right away, this saves a draft, but doesn’t put this text up on the site. This way this will show up if someone else tries to edit.
  9. Translate the text to your language.
  10. When finished. click “publish”.
  11. Click the Page Info tab at the very top and then translate the ‘title’, ‘content’, and ‘description’ into your language (we dont use the other ones).

A couple of important notes

  • Make sure the language displayed in the lower left hand corner is the
    one you intend to edit.
  • do not change the ‘page name’ (!!)
  • the language links on the top of the edit window will show if the
    english version has been modified since the last time a translated
    version has been saved.


English, French, German, Portugese, and Spanish are supported. German does not have anything translated yet, however.

To add an additional language to, someone with sudo access to must edit, and add the proper 2 letter code to the line
bc. languages = en es pt fr de


What about Russian? I have completely translated now.


I tried changing the line in to be

languages = en es pt fr de ru

and it didn’t add Russian. Maybe Elijah knows what to do.


russian is not going to work, because the character encoding is western.


So can you add UTF-8? It is universal for all languages and compatible to western character encoding.


it will be much easier to port everything over to crabgrass than it will be to support utf-8 on :(


Wondering if it’s ok i start to translate riseup help pages in CG this week (to spanish).


tzl: let me ask on #crabgrass if there is a “correct” way to do this. previously, we have been creating sections for each language with this markup:


English version

[<< table of contents -> table of contents]
text in english

Version française

[<< sommaire -> table of contents]
text in french



sounds like this approach will be ok for now. Thanks for the translations!


When i tried to use this macro on spanish translation of GoogleSharing, it doesn’t work right, i’ve to make the Toc by hand. :/


sorry about that… a new release of crabgrass is scheduled for this week, so maybe it will be fixed soon.