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
Task Description and Plan: There is a current issue in the repository that consist of adding option to choose French for the language of the website. In order to do this, I would have to do a direct translation of the words in the i18n .json files, and correlate this change amongst all projects: admin, mobile. Once finished, I will need to test if the page correctly translates its text to French.
Image showing the problem and its room for enhancement:
Risk Assessment: there is a time risk involved with adding this feature, considering it requires manually translating each line. Hopefully I can find a tool that does it automatically for me instead of translating 1000+ lines of text. There is also the risk of bad translation as well.
Image showing that all the items in the French translation JSON are all in English still:
**UPDATE: translation only needed in the admin page, looks as if it has been applied to customer end **
The enhancement was done through researching techniques for translating large JSON files, and while doing so, I came across an article on the azure translator. With this new knowledge I decided to make an Azure account and develop a script from which I could generate the translated text. Once this was translated, I swapped out the previous JSON file in the project and updated the dropdown list to include French as an option.
This was tested by running the application and seeing if the option for French was in the dropdown, and if it effectively alters the text on the screen.
The text was updated successfully, but these errors were encountered:
Task Description and Plan: There is a current issue in the repository that consist of adding option to choose French for the language of the website. In order to do this, I would have to do a direct translation of the words in the i18n .json files, and correlate this change amongst all projects: admin, mobile. Once finished, I will need to test if the page correctly translates its text to French.
Image showing the problem and its room for enhancement:
Risk Assessment: there is a time risk involved with adding this feature, considering it requires manually translating each line. Hopefully I can find a tool that does it automatically for me instead of translating 1000+ lines of text. There is also the risk of bad translation as well.
Image showing that all the items in the French translation JSON are all in English still:
**UPDATE: translation only needed in the admin page, looks as if it has been applied to customer end **
Feature/Bug has been fixed
here is a link to the pull-request:
ever-co/ever-demand#1570 (comment)
The enhancement was done through researching techniques for translating large JSON files, and while doing so, I came across an article on the azure translator. With this new knowledge I decided to make an Azure account and develop a script from which I could generate the translated text. Once this was translated, I swapped out the previous JSON file in the project and updated the dropdown list to include French as an option.
This was tested by running the application and seeing if the option for French was in the dropdown, and if it effectively alters the text on the screen.
The text was updated successfully, but these errors were encountered: