Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[translations] Translate new site #493

Open
1 of 3 tasks
isabelle-dr opened this issue Jun 7, 2024 · 1 comment
Open
1 of 3 tasks

[translations] Translate new site #493

isabelle-dr opened this issue Jun 7, 2024 · 1 comment
Assignees
Labels
documentation Improvements or additions to documentation epic

Comments

@isabelle-dr
Copy link
Contributor

isabelle-dr commented Jun 7, 2024

This is an epic issue intended to plan for translating the site.

Context

gtfs.org has translations in the following languages:

  1. German (de)
  2. Spanish (es)
  3. French (fr)
  4. Indonesian (id)
  5. Japanese (jp)
  6. Portugese (pt) (Portugese Brazilian (pt_BR) is not supported)
  7. Russian (ru)
  8. Corean (ko)
  9. Chinese traditional (zh_TW)
  10. Chinese simplified (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

  • the translations in all the languages above are up to date
  • we have a process in place so that translations are updated in every PR on gtfs.org (i. e. no translation backlog accumulation)

To do

1. Review and update the glossaries.

2. 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.

@fredericsimard
Copy link
Contributor

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
documentation Improvements or additions to documentation epic
Projects
None yet
Development

No branches or pull requests

3 participants