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 need to be updated #580

Closed
ian-ross opened this issue Aug 23, 2016 · 7 comments
Closed

Translations need to be updated #580

ian-ross opened this issue Aug 23, 2016 · 7 comments

Comments

@ian-ross
Copy link
Contributor

Steps to reproduce the error

Select any non-English language in the language menu and browse through the platform.

Actual behavior

There aren't a lot of translations... Most of the translations that there are were done some months ago, mostly to test the multi-lingual messaging machinery. And the translations were done by people in the development team rather than by professional translators, so they're not particularly good or reliable.

Expected behavior

Translations everywhere, at least for all the languages that appear in the language menu.

There are four steps needed to make this happen:

  1. We need to check that all the text we want translated is set up for translation, both in Python source and in the templates.
  2. We need to pull out the source messages and upload them to Transifex.
  3. We need to decide what languages we need to support initially and engage translators.
  4. Once the translators are done, we can pull the translated messages and check that none of the page views have been disrupted by differences in message lengths, etc.

Once the initial translation job is done, we also need to set up some process for maintaining translated message catalogues in future releases

@ian-ross ian-ross added the bug label Aug 23, 2016
@seav
Copy link
Contributor

seav commented Aug 23, 2016

Step 1 above is already filed as #573.

@wonderchook
Copy link
Contributor

Is step 1 a manual process where someone simple reviews all strings?

I'm thinking to test this we do the following:

  • Review strings
  • Pull out the source messages as suggested
  • Have David translate into Spanish
  • Pull translated messages
  • @dpalomino can use the site in Spanish and look for things we've missed
  • Engage translators (this is likely to be more partner based than specifically hiring translators for most languages)
  • Pull translated messages from additional translations
  • Rinse, repeat.

@ian-ross
Copy link
Contributor Author

Yeah, step 1 involves manually looking for all strings that ought to be translated, and checking that they're within _(...) in Python files or within {% trans ... %} or {% blocktrans %} in templates.

I like your plan of getting quick Spanish translations from David: that will give us a good way of spotting where things are missing. And Spanish is different enough to English that it's easy to spot when things really are missing.

Checking the strings is a tedious and error-prone job, so we should probably split it. I don't know how to manage that, but everyone should probably do a bit (where "everyone" = me, Oliver, Eugene, Lindsey, Brian).

@wonderchook
Copy link
Contributor

related to #573

@dpalomino
Copy link

Still not finished (58%), but there are some Spanish translations already in Transifex, I'll keep you posted.

@wonderchook
Copy link
Contributor

@fhpichel the tech part is more or less done, so getting the translations becomes more a programs thing.

@wonderchook wonderchook modified the milestones: Not Scheduled, Sprint 10 Oct 12, 2016
@wonderchook
Copy link
Contributor

Closing this as it isn't really relevant to development. More if other languages are needed translators need to be sourced.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

5 participants