tenants2 Fully internationalize app.justfix.nyc.

Fully internationalize app.justfix.nyc.

Open toolness opened this issue 4 years ago • 0 comments

Now that we've internationalized NoRent.org (#1384), we should internationalize the rest of the platform. This will consist of the following:

[ ] Our dwh app currently looks at raw, localized TextIt strings to determine statistics about follow-up flows; we will need to fix this somehow, e.g. by also searching for the Spanish versions of the string, or using some non-locale-dependent way of identifying user choices.
[x] When we create a new TextIt user, we should set their locale accordingly. (Done in #1639.)
[ ] Actually internationalize all strings on all TextIt flows.

[x] Change the DHCR email to be rendered react-side like the NoRent emails are (#1520).

[ ] Determine the UX for viewing the LOC translation (likely to be similar to NoRent) and implement it.
[x] Convert the LOC letter to be rendered React-side, like the NoRent letter is; it will make it easier to internationalize (#1533, #1534, #1535, #1536).
[ ] Ensure all copy uses the word "home" instead of "apartment".
[ ] Consider saving the user's locale-specific version of their letter like we do with NoRent letters.

[ ] Figure out how to show the user a translation of the HP Action packet, if it's possible.
[ ] Set the user's locale for DocuSign appropriately.
[ ] If the user speaks Spanish, we may need to add something to the EHPA Packet to let the courts know, so they can e.g. ensure that a translator is available.

[ ] Actually internationalize all strings on the Django side.
[ ] Actually internationalize all strings on the React side.
[ ] Ensure that links out to our other sites (WoW, EFNYC, etc) always go to the proper localized version.
[x] Remove the Spanish-to-English locale redirector added in #1498. (At least feature-flag it so we can develop with it disabled!) Update: this was solved by #1552 and #1561.
[x] Develop a strategy for linking to external resources in their native language and/or English. For instance, it would be nice if Met Council on Housing links were in English or Spanish based on the currently active locale; and if a resource is only available in English, we should ideally identify it as being in English if the user has a different locale active. (Update: this is done in #1510, #1545.)
[ ] Figure out a way to translate arbitrary user input to English for e.g. custom issues and harassment details. Exploratory work on this is being done in #1507.
[ ] Figure out what to do UX-wise for the "email the LOC/HP packet" feature. For instance, do we send the email in the user's current locale? Do we include a translation of the PDF, or only the English version?

Jun 02 '20 10:06 toolness