- Translating web pages
- Length of headlines and news-teasers
- Step-by-step guide
- How to use webpreview for translations
- Do's and Don'ts
- More information on translations
- Download all source files and edit them on your own
- Translating subtitles for videos
- Translating Ada & Zangemann book
Translating web pages
The FSFE's work heavily depends on our translators' contributions. They can make our message be heard in the many languages in Europe and the whole world. On this page you will find a short step-by-step guide about how you can help with translations of fsfe.org and other popular FSFE sites, also some Do's and Don'ts and some more detailed information about the coordination between our translators and about the technical background. Further information can be found on our general page about translations.
Length of headlines and news-teasers
https://wiki.fsfe.org/Internal/Publishing/PublicationChecklist A headline has a maximum of 80 characters. (Bonus point when your headline is between 40 - 60 characters)
A teaser is between 200 and 350 characters long. (longer teasers will look bad on our front-page)
A teaser is blank text without any link. (any link people can click in the teaser will lead them to another page than your article)
In this example, we want to translate https://fsfe.org/contribute/spreadtheword.en.html into Spanish. The screenshots may help visualise some steps (be aware that the content of the file may have changed meanwhile, or that your setup may look different!).
Download the .xhtml file. In the git you will be able to click on Raw and then with Ctrl+S or right click and save page as save the file to your computer (in this case https://git.fsfe.org/FSFE/fsfe-website/raw/branch/master/contribute/spreadtheword.en.xhtml).
Write a short e-mail to firstname.lastname@example.org (you should already be subscribed to this mailing list) and tell them that you start with the translation. Please open for each new page a new thread and add your two letter Language Code in the mail subject (e.g. [ES]) as well as the name of the file that you are translating. For example "[translating] [ES] spread the word page"
Open the downloaded file with a text editor (for example gedit, Kate, Mousepad on GNU/Linux operating systems, Notepad++ on Windows).
Translate all English text outside the HTML tags into your language. For example: <p><a href="/contribute/">Contribute</a></p> should become <p><a href="/contribute/">Colabore</a></p>. (Screenshot)
Please change the two letter Language Code of the translated file from "en" to the one of your language (for example Spanish = spreadtheword.es.xhtml).
Afterwards, please reply to your thread in email@example.com and ask other people to proofread your file. If everybody agrees, it will be uploaded by others on the mailing list. (Screenshot) For the subject line it then looks like this: "[needs proofreading] [ES] spread the word page".
When proofreading a translation or the English original please add [proofreading to the subject line. For example "[proofreading] [EN] spread the word page" or "[proofreading] [ES] spread the word page". This makes it easier for the translators to identify the status and if the message is relevant for them.
If possible check how the xhtml file looks like when it is compiled with our webpreview/tool.
If you know how to use git and also have an account you are welcome to make a Commit and Pull Request for git.fsfe.org If you want to learn how to use git have a look at the First Steps with git wiki-page. After you have committed your Commit or Pull Request make sure to add this information to the subject line of your emails. So the new subject line should look like this: [Commit] [ES] spread the word page
Note: You are also very welcome to add the <translator>Your Name</translator> tag at the end of the translated .xhtml file above the line saying </html>. See also under Contributing missing translations on this wiki page.
Tags for subject lines
* [needs translation/proofreading] [EN]: Initial message sent by staff people, with no intention of translating the text themselves
Tags for subject line including translations
[translating] [LANGUAGE CODE]: used when a translation is started
[proofreading] [LANGUAGE CODE]: used when proofreading
[needs proofreading] [LANGUAGE CODE]: used after the translation is finished and needs proofreading
[translated] [LANGUAGE CODE]: used when the translation is ready for publication (after proofreading)
Helpfull tools: Wordlist
Here you find wordlists for different langugages. The list contains some frequently used words and how we prefer to spell them.
How to use webpreview for translations
Take the link of the page you want to translate/proofread from fsfe.org website (or from git source or pull request), paste it into webpreview and press Preview file button. You can also copy/paste the content of the x[ht]ml file.
Press Proofread/Translate button and choose Translate if you want to start a new translation (the language selection is optional but recommended for the future spellcheck functionality), or Proofread if you want to proofread the existing page.
Make your translation/proofread (the page is automatically saved every minute, or you can press again Proofread/Translate button to manually save it). You have a character count for "Title" (max 80) and "Teaser" (max 350). They become red when you exceed the maximum.
Share the number of the PAD or its link (the number after "PAD:" is an hyperlink, you can right click and "Copy Link location") to the Translator mailing list.
- Well done!
Do's and Don'ts
- Make sure that there is not already a translation of the page you want to translate. This would then only create unnecessary work for everyone involved and would probably be quite frustrating for you.
- Proper names of a organisation or a project are not usually translated. BUT however you can check on the linked project side if they have translated their name and then continue to use this one.
- If you notice that there isn't an answer within the next week, please do send a reminder as it sometimes is a bit busy on the mailing list and people might overlook an email.
- Please stick to the proposed subject format: [Language Code] name of the webpage/file
More information on translations
Styleguide for English Translations and Text
There is also a styleguide for English versions in the making. Have a look here for more information.
Everybody can contribute translations
All source files (i.e. all XHTML and XML files) are publicly available for download, so everybody can spontaneously contribute a translation without having to register anywhere. However, whenever you start a translation and expect it to take longer, please write a short note to the Translators mailing list to avoid that somebody else starts to work on the same text simultaneously.
Contributing missing translations
If you have a page open in your web browser that has not yet been translated to your language, scroll to the end of the page, click on the Source code link and save the file you get there. You will get the English XHTML file. Rename the file to carry your language code instead of the "en" code, and open it in a text editor. Now, translate all text in the file that is outside the <…> marks; do not change anything inside these marks (the text inside the marks are XHTML commands that influence the structure of the resulting web page).
At the end of the file there will be a line saying </html>. Immediately above this line, add a line saying <translator>your name</translator>.
When you are done, send the translated file to the Translators mailing list. Other members of this list can proofread the translation, and somebody on that list will ultimately post it to the server. Updating outdated translations
If you have a page open in your web browser of which the translation is outdated (indicated by a note at the top of the page), scroll to the end of the page, click on the Source code link and save the file you get there. This file is the (outdated) translated version. Next, use the English link at the top of the page to jump to the English version of the page and click on the Source code link there, too. The file you get there is the (up to date) English version. Now you can compare both files and update the translation. Please notice that everything inside the < … > marks may not be translated.
Alternatively, you may also use the web-based source repository on the fsfe-website Git interface to create diffs, and to see the latest updates for all source files.
When you are done, send the translated file to the Translators mailing list. Other members of this list can proofread the translation, and somebody on that list will ultimately post it to the server.
Finding out what needs work
Currently there's no comfortable interface to show files which do not have a translation at all. You can browse on fsfe.org in your language and look out for pages which you like to see translated – just look out for the red warning box above the content body. Alternatively, feel free to ask the other translators how you can help.
Download all source files and edit them on your own
You can also download all source files at once. Please have a closer look at how our web pages are built. Our Web team provides an overview of the systems behind fsfe.org and other popular FSFE websites.
Translating subtitles for videos
Translating Ada & Zangemann book
The source files for the FSFE's childrens book "Ada & Zangemann" can be found in the git repository. Please feel free to reach out to the translators mailing list if you need help or have any question about the translation.
For more advanced translators we also offer direct write access to the FSFE website source repository. Please refer to the Web team's general information page and the detailed wiki page on editing the website's source.