GPG guide/Translation Guide
Contents
Translating Email Self-Defense
So you want to translate the FSF's guide to email encryption? Great!
First, send a message to campaigns@fsf.org stating your intention. We ask that you not begin translating until you receive a reply, so that we can connect you with other translators working in your language and avoid reduplicating effort.
Once you get the go-ahead from the FSF, send your SSH public keys to sysadmin@fsf.org. When they tell you that they have given you access to the git repository, you are ready to begin.
Things to do
Text on all pages
- index.html
- mac.html
- windows.html
- next_steps.html
- confirmation.html
Text Instructions
You don't need to translate anything that is commented out.
Make sure to translate the text in the sharing URLs, which are linked to from the #EMAILSELFDEFENSE hashtag on the guide pages and the text at the top of the infographic page.
Language Picker
On all pages with a language picker, modify the language picker so that your language is the active class instead of English.
Graphics
- join and donate buttons
- infographic and "view and share our infographic" thumbnail image
- all inline images
Graphics Instructions
You can get the image source files from the source package in the /en directory. Translate them, using the closest you can find to the fonts in the source package for your language, then create the pngs from the sources.
Next you'll add your images to the static directory. This directory is a submodule, so you'll need to run 'git submodule update' from the root directory of the repo before working it. Then navigate to /static/img and create a directory named after your language, like en. Put all your translated pngs into that directory. Even if an image does not have text, copy it into your language's directory in static. For committing your changes in static submodule, see the simple instructions at https://libreplanet.org/wiki/GPG_guide/Checking_Out
Once you're done with this, edit the HTML in your language's pages to call the images from your language's directory in static. Even if an image does not have text, call the copy in your language's directory.
Source package
You can use the .zip source package in /en as a model for this. Make sure to translate the README as well. Even if an image isn't translated because there is not text, it should still be in the source package for your language.
The source package also includes the text of the messages for Edward the reply bot, which you should translate as well. This is the only place on the site where Edward's text is.
When you are done, compress it and commit it as a single archive.
Remember to update this when you change an image.
Links
If a link points to something that you can easily find a translation of in your language hosted by the FSF or GNU, please modify the link to point to it. If you find a translation by someone else, please let the FSF know and we will review the translation to see if we can link to it instead.
Make sure to test all links.
Preserve HTTP/HTTPS.
Attribution
If you'd like to get credit for your work, add your name to the commented-out attribution line in the footer and comment it back in. Make sure to do this on all pages.
Review
Please have at least one person review everything that is translated, comparing the original and target texts. This person needs to be able to speak English as well as the target language. If a piece of text was translated by two or more people working as a team, that counts as well. In short, at least two sets of bilingual eyes should have seen everything before the translation is complete.