Closed mcfrank closed 1 year ago
@mcfrank I've updated the field names for English. For other languages the Child's Ethnicity translation will automatically move across and be translated as previously. If these languages had previously translated Child's Ethnicity and Child's Race, this means that they'll now be wrong.
I am happy to review the French, Dutch and Spanish and ensure they are right. I need translations for Korean and Hebrew. I think I have emails for the two main contacts so I'm happy to make contact if you want
I have now worked through all instruments and I think the translations are good across all languages. Best check would be for native speakers to confirm within development.
Please note, I have not changed the field names, only the names displayed to users because changing the field names is would require very significant testing effort
@HenryMehta Should I be seeing this in outputs on dev?
@vmarchman yes, you should. But I did this in August so I'm not 100% certain what I did now.
We currently have two fields -
child ethnicity
andchild hispanic latino
. These are labeled incorrectly and need to be swapped tochild race
andchild ethnicity
(which means hispanic/latino). Also the "no ethnicity" answer should be corrected to "no race".