Open isabelle-dr opened 1 month ago
To add to the "3. Set-up the process to maintain the translations moving forward." step, I have found out it is possible to automate the translation of files when a PR is created, the files will be added to the same PR automatically. Someone will then have the opportunity to revise them for contents, and grammar/spelling if they are able/wishing to.
I have an action ready to test when Elrond is officially published.
This is an epic issue intended to plan for translating the site.
Context
gtfs.org has translations in the following languages:
de
)es
)fr
)id
)jp
)pt
) (Portugese Brazilian (pt_BR
) is not supported)ru
)ko
)zh_TW
)zh
)Given that our previous translation system was very time intensive, @fredericsimard has worked on a new tool to manage translations.
As part of the new gtfs.org release, we've decided that it would be quicker to re-translate the whole site from scratch instead of trying to reuse what we already have.
Scope for translations
To do
1. Review and update the glossaries.
code formatting
in the glossaries2. Translate the site in every language described above. Note that ideally, the output of the translations is final and if we need to make changes, it should be done via the glossaries. That being said, we received good feedback feedback on the Japanese translations from Google, and it would be nice to try and integrate them. They are in this document.
3. Set-up the process to maintain the translations moving forward. We want to avoid having a translation backlog, so we'd like translations to be done in every PR, as a requirement before merging.