Calculate your turnip price patterns and gain the most from the stalk market!
You can find the live calculator here.
1.1: Clear data button! Please use it responsibly!
1.2a: Fixed pattern ranges
1.3: Animations fixed. New icons #2. New horizontal marker for buy price #5.
1.4: Guaranteed Min #10. Localization Support #12. New Currency Icon #11.
1.4b: A lot of new translations! #8 #15 #16 #18 #19 #20 #21 #22 #23 #24 #25 #26 #27
1.5: Styling update! Thank you! @mtaylor76 #24
1.6: Translation switcher! I can't thank you enough @mtaylor76! #33 New vector for bells currency! #34 New Translations and Translation Updates! #28 #30 #31
1.7: We have domain! Confirmation of erase data button! #35 New Translations and Translation Updates! #37 #36 #38 #39 #40 #41
1.8: Pending changelog Share button! New translations! Service Workers! Smaller website size!
This app supports dynamic localization using i18next and react-i18next, with i18next-browser-languagedetector to automatically detect the user's native OS language preferences and switch the app's language accordingly.
As features are added to the calculator, they'll most likely not be localised immediately. To localise any new text in the app, make sure to first wrap the text in the t() method taken from the useTranslation() hook. Then, in your language's translation.json, add a new JSON key/value pair with the key used in the t() method, using your translated text as the value.
For example, let's say we're adding a new button that says "Show Current Pattern". In the component where that text would be displayed, you would instead write t("Show Current Pattern"), wrapping the statement in brackets {} if it were part of JSX code.
Then, to add a translation to your language, you'd go to your languages translation.json file, and add the following line (using Spanish as an example):
"Show Current Pattern": "Mostrar Patrón Actual",
If no key is specified in the localization files, the app will simply display whatever text is passed into t(), to avoid errors.
To localise the app to a new language, the following simple steps need to be done:
- Create a new folder under
/localesfor your language using the standard two-letter IETF language code for your language (e.g.esfor Spanish,zhfor Chinese). Keep in mind, the language code often differs from the more commonly known country code. For example, the country code for Korea iskr, but the language code for Korean isko.- Dialect codes are supported (e.g.
en-GBfor British English andpt-BRfor Brazilian Portuguese), but be sure to avoid hyphens (-) in variable names. As a reminder, hyphens can't be used in JavaScript variable names. When in doubt, stay consistent with existing code.
- Dialect codes are supported (e.g.
- In the newly created folder, copy and paste the
translation.jsonfile from one of the other languages. - Edit the
translation.jsonfile to translate each untranslated JSON value to the appropriate translated equivalent in your language. - In
/src/i18n.js, create animportstatement for your language, importing thetranslation.jsonfile you just created. Follow the pattern used by the existing statements. - In the same file (
/src/i18n.js), add your language to the list of languages inside theresourcesobject within thei18n.init()method, following the pattern of other declared languages, and using the same two-letter language code you used for the folder name in the first step. - Lastly, to add your language to the manual language switcher on the page, make sure to edit the
Localizercomponent at/src/Localizer.jsx. Add a tuple for your language to thelanguagesarray, with the first value being your two-letter language code and the second value being the name of your language, in your language.- For example, to add Japanese to the list, you'd add
["ja", "日本語"],
- For example, to add Japanese to the list, you'd add
The localization is now ready to deploy and will appear to users who use your language for their browser.