-
Notifications
You must be signed in to change notification settings - Fork 0
How to Test the App's Translations in Chrome
This document will detail how to test the app's translations in Chrome. It will cover how to efficiently test in a development environment as well as in production.
- To test your translations in a development environment, we recommend changing the
detectLanguage
function insrc/lib/i18next
to always return"my"
. This is whatnavigator.language
returns in Chrome if your default language is set to Burmese. After refreshing, text containing translations should be translated to Burmese.
To test translations in a production environment, you'll need to temporarily set your browser language settings to Burmese. The following procedure will detail how to do this for Chrome.
-
Open your browser's settings page. You can do this by clicking the top right triple dot icon and hitting "Settings"
-
When on the "Settings" page, search for "Language" and click the dropdown to expose a section labelled "Order languages based on your preference"
-
Press "Add Language" and select "Burmese" if it not already there. Then, put "Burmese" as the top choice so that it's the most preferred.
-
(Optional) Open an incognito window and navigate to
https://meepanyar.netlify.app
and make sure that the app is translated -
Once finished testing, make sure to move "English" (or whatever language was originally your most preferred) back to its original spot.
- Creating a New User and Assigning them a Site
- Adding or Updating or Deleting an Airtable Column or Table
- Testing Translations in a Production Environment