Hi devs, I would not mind to reveal my particular interest in implementing the idea of in-page localization. As for me, this is correctly to give opportunity for translators to see their translations precisely in context of the page. When I was reading the wiki page for this project<https://wiki.openmrs.org/display/projects/In-page+Localization+(Design+Page)>, some ideas came to my mind and I'd like to share them with you right now.
1. Use bookmarklet <http://en.wikipedia.org/wiki/Bookmarklet> instead of Firefox plugin. In my opinion it's not the best practice to set bounds for potential translators which browser to use (apriori, it's his prerogative). We can put this bookmarklet in the bottom of the page at strip with languages. 2. Allow translators *not only locally save their translations*, but also *commit them to OpenMRS serve*r (just like many popular translations services do, for instance Amanuens <http://amanuens.com/> or Transifex <https://www.transifex.net/start/>). For this we can create appropriate DWR service and post translations data using JQuery, for example. 3. As for issue of synchronization openmrs:message tags values content with message.properties files (#2 and #3 tasks on wiki page of project), I think it would not hurt, if we create corresponding ant targets, which will be responsible for both these tasks. It will be great if we add antrun plugin <http://maven.apache.org/plugins/maven-antrun-plugin/> to our maven program object model to launch those targets from maven too. So, we won't limit developer what build manager to use. Cheers, Mykola _________________________________________ To unsubscribe from OpenMRS Developers' mailing list, send an e-mail to [email protected] with "SIGNOFF openmrs-devel-l" in the body (not the subject) of your e-mail. [mailto:[email protected]?body=SIGNOFF%20openmrs-devel-l]
