I'm developing a form in Nepali with case sharing. I created the form with
default choice values in English and they show up in the case list as
English instead of the translated version of Nepali. I have been testing
creating choice values in Nepali unicode instead of English. Do you know if
this will cause problems?
The ideal situation would be to have the choice values in the case list
translated based on the default language of the user. Is there a "best
practice" when dealing with multiple languages in a case list with choice
questions?
Yes, we support unicode fonts in choice values. You can write the choice
value in either English or Nepali, and we have created functionality for
translating the choice values for each question.
So, to establish Nepali translations for the choice values, change the
language to Nepali and navigate to the Case List tab for your module. Add a
new list item and pick the property you’d like to translate. Choose ID
Mapping for the format, then click Edit and add Key -> Value mappings
(choice value -> translation) for each of the choices for that question.
Let us know if you have further questions.
Cheers,
···
--
Nate Haduch
Technical Support Analyst
Dimagi, Inc | 585 Massachusetts Ave | Suite 3 | Cambridge, MA 02139
web: http://www.dimagi.com/
I'm developing a form in Nepali with case sharing. I created the form with
default choice values in English and they show up in the case list as
English instead of the translated version of Nepali. I have been testing
creating choice values in Nepali unicode instead of English. Do you know if
this will cause problems?
The ideal situation would be to have the choice values in the case list
translated based on the default language of the user. Is there a "best
practice" when dealing with multiple languages in a case list with choice
questions?
"to establish Nepali translations for the choice values, change the
language to Nepali and navigate to the Case List tab for your module. Add a
new list item and pick the property you’d like to translate. Choose ID
Mapping for the format, then click Edit and add Key -> Value mappings
(choice value -> translation) for each of the choices for that question."
Sincerely,
Craig
On Tuesday, September 30, 2014 1:41:11 AM UTC+5:45, nhaduch wrote:
Dear Craig,
Yes, we support unicode fonts in choice values. You can write the choice
value in either English or Nepali, and we have created functionality for
translating the choice values for each question.
This is documented in the following wiki, and I’ll discuss a quick use
case below: https://confluence.dimagi.com/display/
commcarepublic/Case+List+and+Case+Detail+View+Configuration
So, to establish Nepali translations for the choice values, change the
language to Nepali and navigate to the Case List tab for your module. Add a
new list item and pick the property you’d like to translate. Choose ID
Mapping for the format, then click Edit and add Key -> Value mappings
(choice value -> translation) for each of the choices for that question.
Let us know if you have further questions.
Cheers,
--
Nate Haduch
Technical Support Analyst
Dimagi, Inc | 585 Massachusetts Ave | Suite 3 | Cambridge, MA 02139
web: http://www.dimagi.com/
I'm developing a form in Nepali with case sharing. I created the form
with default choice values in English and they show up in the case list as
English instead of the translated version of Nepali. I have been testing
creating choice values in Nepali unicode instead of English. Do you know if
this will cause problems?
The ideal situation would be to have the choice values in the case list
translated based on the default language of the user. Is there a "best
practice" when dealing with multiple languages in a case list with choice
questions?
Thank you!
Craig
--
You received this message because you are subscribed to the Google
Groups "commcare-users" group.
To unsubscribe from this group and stop receiving emails from it, send
an email to commcare-user...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
This is exactly what I was looking for.