Spanish Site-Wide Language Translations

[villahm206]

Starting a new thread for SITE WIDE language (Not including the translation of Tasks) per Colin's Request.

Here is the document with global site language translated to Spanish:

https://docs.google.com/spreadsheets/d/17SNHgkej7qeyG4S31SmPpARYbSllCIjnFMZ-8XSw5U0/edit?usp=sharing

The translators are ready to do a QA check once these are updated - when do you think that will be? Colin suggested that we upload the spanish but do not make it accessible to all users until we have run Quality Assurance.

[jakelowen]

@jrazmi see backend /utils/localization/locales/es/common.json to see if this meets your needs. The script to generate is utils/localization/makeLocalizationFile.js which points to a direct export of the google doc linked above. It generates ZH/TL/EN as well.

[jakelowen]

Update: Translations are being added in for common site wide language. We will have these up on the staging environment for your review mid/late week next week, 2/13/2020. We'll ask you all to review the staging site in English and Spanish prior to pushing the deployment live.

[CaptainTeft]

In case @villahm206 has lost the link, staging site URL remains https://census-ro-frontend-staging.herokuapp.com/

[villahm206]

@jakelowen is this in track for today?

[jakelowen]

@villahm206 - Yep! @jrazmi and @elmather89 just wrapped it up. To review:

Step 1: visit and log in to the staging site: https://census-ro-frontend-staging.herokuapp.com/ Step 2: In top nav bar under account set your language preference. Step 3: use the site as normal.

You will note several places where the static text is NOT translated. To fix this, go back and add those entries in the original spreadsheet linked above and fill in those gaps. Ping us here when updated and we will import the new translation file.

[CaptainTeft]

@jakelowen @jrazmi @elmather89 can we make sure Heather@equitabledemocracy.org and lmeng@interproinc.com have sitewide admin permissions on census-ro-frontend-staging ?

[jakelowen]

@CaptainTeft - Heather does already. Lmeng will need to register on staging before I can grant global admin perms.

[villahm206]

@jakelowen Sorry, I thought Lmeng had done it already.

As far as the terms that are not translated... there are no blank spots in the spreadsheet...? I see several terms that are on the spreadsheet that are not translated. i.e. "Page, My Contacts, All Contacts, Filter". I also see a couple terms that aren't on the spreadsheet at all, and naturally those aren't translated, but I don't want to audit them until we have all of the spanish up.

This is the one y'all are working off of, right? https://docs.google.com/spreadsheets/d/17SNHgkej7qeyG4S31SmPpARYbSllCIjnFMZ-8XSw5U0/edit?usp=sharing

[jakelowen]

@jrazmi , @elmather89 - Any thoughts here?

[villahm206]

@jrazmi , @elmather89 - Any thoughts here?

Just want to boost this -I'd like to be able to have our translation company review the translations in-format very soon.

[jrazmi]

@villahm206 - Reviewing today will try to get it all sorted out so you can have the translation company review.

[jrazmi]

@villahm206 - https://census-ro-frontend-staging.herokuapp.com/ Staging site is updated with the translations provided in the doc. There are still a few missing, but as you add more in there we can pull it down and add them in as needed.

If you're good to go - let us know and we'll push this up to the live site.

[villahm206]

@jrazmi I see there's a second tab in the google doc that says "need to be added to the translations spreadsheet" and some of them are checked as "Coded", but aren't actually updated in the site, i.e. "My Contacts", "Create New Team".

Do I/the translation team need to be the ones to identify which terms are outstanding? Or do you have these somewhere?

I don't want to add them to the new tab until it's clear what's truly updated and what's not.

[jrazmi]

@villahm206 Sorry for the confusion there. Coded is a term for @elmather89 and I to keep track of what we've updated on the app. It takes a specific function call on the language that we need to update everywhere the language shows up. If there aren't translations, then that function will default to the English. So for the second tab - we've gone in and updated the code for those - but since we don't have any spanish translations yet - its just showing as english.

I don't have a master list of the translations outstanding. I can drop some in this doc as I'm going through the app, but if you all can comb through it and figure out what's left that would be a tremendous help.

[villahm206]

@jakelowen Here is the translators' email that needs global admin access: Interpro.PT@gmail.com She said she already signed up though I can't seem to confirm.

[jakelowen]

I've added the user with the above email as a global admin. Thanks @villahm206

[villahm206]

@jrazmi I added to the list of terms that were not in the initial translation order. I will check in with translators about next steps.

[villahm206]

I've added the user with the above email as a global admin. Thanks @villahm206

Thanks @jakelowen!

[villahm206]

@jakelowen @jrazmi I've uploaded the additional spanish translation for the english terms that were missed in the first round of translations into the spreadsheet.

I left them in the "Need to to translations spreadsheet" tab so that I didn't inadvertently mess anything up.

After these are implemented, we will do QA with the translation company and we can push it to production.

[villahm206]

@jakelowen @jrazmi, the additional spanish translation terms are uploaded into the spreadsheet. Please let me know when they are on the staging site so I can let the translators know they can get started on their Quality Assurance process