Thanks again @calurduran for the guidance.
All GMC members, and Rocket Pool community at-large are invited to take the following information into consideration for the assessment of our team’s proposal as it appears that a clarification is required with some added notes:
This proposal is made to localize the primary section in protocol’s documentation into 5 languages (OFD), and serve as a proof of quality for the translation of all remaining written content.
Given the undeniably sobering market conditions and relatively high cost of translation into 5 languages, poor quality would not be a tolerable risk if the scope involved entire documentation (approx. 100k). Therefore, our team is glad to offer the Rocket Pool protocol the opportunity to have its primary content translated by a highly experienced team, and depending on the output, assign the remaining work to an already-proven team by avoiding risk of any loss in terms of both money and time, and benefitting from the advantage of providing feedback throughout this process.
The scope of translation:
- ‘Overview’: Main informative section in the documentation aiming to guide new users around the basics of protocol, complemented by FAQ and Glossary.
While the scope was initially limited to ‘Overview’ section excluding any external links (for the sake of orderly completion of translated sections), our team decided to involve one article for the community to test the advantages, and thus necessity of translating the Medium content (blog articles in addition to Explainer series).
- ‘Rocket Pool — Staking Protocol Part 1’: A Medium article that is specifically recommended to be read by users under the ‘Introduction’ part of ‘Overview’ section.
That being said, the rate per word is $0.1 (or RPL equivalent) including the entire translation and review work. Rocket Pool is welcome to offer any changes to the proposal including selection and/or extension of translation content, selection of languages, or any other special requests.
The exact word count will be finalized at the initiation of project as files in the protocol’s repository will be the most accurate source.
Regarding considerations suggested by @Dondochaka:
We are planning to use Crowdin as a CAT tool for the entire project. Crowdin offers various integration capabilities such as synching translatable content from the protocol’s repository with our project so that you may receive translations as pull/merge requests.
The formats available are listed here.
New English content may be copied as is to all local pages until the relevant translations are complete and uploaded to RP repository.
All translations are saved in a sort of database file called Translation Memory [TM], which speeds up the entire process and improves consistency. TMs can be used for future projects as a tool to pre-translate files (i.e. applying the saved translations to the identical files). GMC is welcome to ask further questions with regards to use of CAT tools.