-
Notifications
You must be signed in to change notification settings - Fork 22
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Documentation] Translation for keys with dynamic values #1444
Comments
@Dinesh2019 also mention the form name, steps to reproduce the issue. I dont see trnaslation for 'should be 90, or less than 90' in the json file. Is the error message dynamically generated? from some rule? |
@mahalakshme this issue is happening will all the translations mentioned as not yet in this sheet in column " |
@mahalakshme here is the json file |
It will work when translations added for keys: numberBelowLowAbsolute and numberAboveHiAbsolute |
|
We have uploaded the translation in the lokalise for some sentence we have translation but not displayed in the cilent app.
Env : prod
org : apfodisha
user : dinesh@apfodisha
Steps to reproduce :
1.Upload the bundle in the lokalise
2.Login to the cilent app
3.Change the language to odisa
4.enroll the pregancy program
5.Under the weight give the value as 100
Expected : error should be displayed in the odisha language
Actual : still displays in english
Refer screenshot :
file uploaded in lokalise :
no_filename.json
form details :
Pending for translation.xlsx
Root cause:
Its because the above kind of messages which can have dynamic values, doesn't need translation for each msg. Instead the generic keys needs translations:
numberAboveHiAbsolute
andnumberBelowLowAbsolute
AC:
Analysis note:
I understand the difficulty of moving documentation from docs to readme. It was so because of a different process agreed with other teams. Going forward we can update directly in readme.
The text was updated successfully, but these errors were encountered: