Registration is open. Server is NOT hosted by the FSFE. However, if you create your account with your FSFE.org email address you will get commit access.
- Content: Proposal for an improved process for the translation of the FSFE.org website
- Date: Summer 2016
Author: Julien Pivotto <firstname.lastname@example.org>
- Progressively translate FSFE.org using po files, instead of Xhtml
- Reduce the translators' efforts to get involved in translations, by using a WebUI
- Remove the barriers for new translators to join, by using a WebUI that allows anonymous suggestions
Translation is stored in .po files. It means:
Changes in original version are identified atomically (fuzzy) -> No need to review the whole file to know what has changed
- Translations can be easily reused across multiple files (however we will limit that for files in the same directory)
- Focus only on text, not on XML
- No more mistakes in XML/XHTML structure as it is generated automatically
Translation can be made in a WebUI. It means:
- Translate from everywhere
- Get an up-to-date overview of what can be done and what needs to be done
- Easily review what is fuzzy / vote on anonymous suggestions
For Web team
Concerning the build process, we keep everything as it for the moment.
There will be a WebUI to manage.
Proof Of Concept, (main) software used
A Proof of Concept has been installed on https://weblate.roidelapluie.be
- It runs against selected files, on the test branch
- It is connected to the SVN
- Registration is open (click the register button)
How can we give credits to translators?
We *will* add the 'translators' xml element back. This is still WIP.
How to prevent two people working at the same time on the same translation?
By default, when you start working on a translation, that translation is locked for 15 minutes. You can also take the lock manually. See upstream documentation.
To Do List
- Get Weblate patches merged upstream
- Credit translator
- Update PO files on pull
- Pull on a regular basis