I'm pretty sure the way that we implemented the translations in
HtmlFormEntry is that tags that support localization will:
1. Look for a translation in the <translations> section. If nothing
found, then:
2. Look for a translation in across all of the OpenMRS message
properties. If nothing found, then:
3. Return the text as is.
So, if you can find a way to manage all of your messages in separate
messages.properties files (eg. in a module), you should be able to refer
to these messages from your htmlforms and have the translations appear
as specified. I haven't tried this myself, but I think in theory it
should work...
Mike
On 04/17/2012 12:26 PM, Ellen Ball wrote:
At PIH, we normally provide multiple languages (English and French) on our
paper and html forms. The translation tag is available, but we rarely use it.
Since screen real-estate is cheap, many of our htmlforms show the text in
both languages. We might show French in black font followed by the English
in italicized grey. If the paper has enough space, we also include both
languages on the form. It's not a perfect system, but the simplest to maintain.
It would be great to have a cleaner method.
Regards,
Ellen Ball
Partners In Health
_________________________________________
To unsubscribe from OpenMRS Implementers' mailing list, send an e-mail to
[email protected] with "SIGNOFF openmrs-implement-l" in the body
(not the subject) of your e-mail.
[mailto:[email protected]?body=SIGNOFF%20openmrs-implement-l]
_________________________________________
To unsubscribe from OpenMRS Implementers' mailing list, send an e-mail to
[email protected] with "SIGNOFF openmrs-implement-l" in the body
(not the subject) of your e-mail.
[mailto:[email protected]?body=SIGNOFF%20openmrs-implement-l]
