You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Replace English with translation keys in the component file
The file to change is src/components/about/DataPage.js.
To test, we expect our helper script to say all of these translation keys which we see on hover under i18n_viz=1 in the live site, are in the component file - run this command:
Now you can look at the localhost vs. beta site, and localhost vs. live site, in English and French. The content should be the same!
You can just look at them, or also, comparing text is a good trick - switch to Reader View, copy text from the site, save to a text file, and compare as text files.
Submit for review
Don't add any keys yourself in this issue since we will do that later - leave English in the source code, and optionally you can make a new issue that reminds us, but we'll do that later.
The text was updated successfully, but these errors were encountered:
Part of #538.
The /data shows content that used to be spread through /data and /datasets on the live site. See how the translation keys are used on the live site: https://fallingfruit.org/data?i18n_viz=1
https://fallingfruit.org/datasets?i18n_viz=1
Implementation steps:
The file to change is
src/components/about/DataPage.js
.To test, we expect our helper script to say all of these translation keys which we see on hover under i18n_viz=1 in the live site, are in the component file - run this command:
We have a script for this:
Now you can look at the localhost vs. beta site, and localhost vs. live site, in English and French. The content should be the same!
You can just look at them, or also, comparing text is a good trick - switch to Reader View, copy text from the site, save to a text file, and compare as text files.
Don't add any keys yourself in this issue since we will do that later - leave English in the source code, and optionally you can make a new issue that reminds us, but we'll do that later.
The text was updated successfully, but these errors were encountered: