Support for language translations and date formats
Description This PR adds multilingual support using i18n. Now, new languages can be added simply by creating a new folder inside /public/locales, named with the language code (e.g., en, es, de, it, etc.). For example, to add German, just duplicate the en folder (or any other existing language folder) and translate the JSON files inside it. No code modifications are required to enable a new language.
Main Changes Added i18n support with JSON-based language management. Translation structure located in /public/locales/{lang_code}/.
New Environment Variables (.env)
#********* DATE FORMAT *********
DATE_FORMAT_VARIANT_1="dd-MM-yyyy"
DATE_FORMAT_VARIANT_2="dd MMM yyyy"
DATE_FORMAT_VARIANT_3="dd MMM"
DATE_FORMAT_VARIANT_4="dd MMM"
DATE_FORMAT_VARIANT_5="dd MMM, yyyy"
Preview
@Rosso2004 The PR is awesome and I would love to have it in Split Pro, but I would wait until there are more collaborators added to the project that would actually allow us to merge this. And I could take a swing at making this type safe once that happens
@Rosso2004 I have been added as a Collaborator so we can proceed with the review and merging the changes :)
Thank you so much
Hi, need help with this PR?
It appears abandoned, feel free to fix the raised issues and sync with the main branch, so we can continue with the review and merging
Hi @krokosik , the PR is far behind the main and there are many conflicts, I will try to see if it is easy to solve otherwise I think it is easier to start again from the main and carry the various changes by hand.
@marcosinigaglia sure, if you have any questions about changes in main, let me know. I will also make a PR soon with some refactors that include string utils which will probably make it easier
Closed in favor of #259