Darius, I think neither sounds much harder than the other one. Which of the two is better for OpenMRS because we'll probably go with that one.
Joaquín ___________________________________________________________________ Gerente de Desarrollo, eHealth Systems <http://www.ehs.cl/> Research Fellow, Escuela de Medicina de Harvard <http://hms.harvard.edu/> Moderador, GHDOnline.org <http://www.ghdonline.org/> On Thu, May 3, 2012 at 9:01 AM, Roberto Ramos <[email protected]> wrote: > Thanks for replying!!, > I'll see how to make changes in the second way you told me and I notice as > I was. > > Gracias por responder!! , > voy a ver como hacer los cambios de la segunda manera que me planteaste y > te aviso como me fue. > > > > 2012/5/2 Darius Jazayeri <[email protected]> > >> Hi Roberto, >> >> Thanks for the reminder. (I lost this thread over the weekend...) >> >> Unfortunately it looks like the code is referencing a "cohort" portlet >> that is currently in core. >> >> Two possible fixes: >> >> Possibility #1 (maybe easiest for you to code, but requires deploying >> updated core OpenMRS): >> make changes in trunk, and we'll backport them as far as the OpenMRS >> version you're using. The relevant file is: >> /openmrs/trunk/webapp/src/main/webapp/WEB-INF/view/portlets/cohort.jsp >> >> Possibility #2 (better in general, maybe easier for you to deploy because >> the fix is just to the module) >> override the cohort portlet from the reportingcompatibility module (it's >> supposed to be in that module anyway) and make the language changes in the >> reportingcompatibility module. >> >> Are both options clear? Do you know which one makes more sense for you to >> do? >> >> -Darius >> >> >> On Wed, May 2, 2012 at 12:52 PM, Roberto Ramos <[email protected]> wrote: >> >>> Hi, I haven't had a reply to my email below so I wanted to send it again. >>> >>> >>> 2012/4/27 Roberto Ramos <[email protected]> >>> >>>> sorry, forgot to include the following text! >>>> >>>> And yes Darius i can look the source code and I have not found the >>>> files to translate, please would need if you know what they are. >>>> Could I use the same function I used in translating the reporting >>>> compatibility module to place the phrases in the message.properties >>>> file. >>>> >>>> Thanks!! >>>> >>>> >>>> 2012/4/27 Darius Jazayeri <[email protected]> >>>> >>>>> Hola Roberto, >>>>> >>>>> Are you a developer? Do you have the capacity to look at the source >>>>> code for the reporting compatibility module and identify where things are >>>>> hardcoded (and ideally fix that)? >>>>> >>>>> -Darius >>>>> >>>>> On Fri, Apr 27, 2012 at 10:47 AM, Roberto Ramos <[email protected]>wrote: >>>>> >>>>>> Hi all, i've been translate the module reporting compatibility >>>>>> 1.5.4.1, but i found parts of code that are in hard code. >>>>>> Attached a picture to see the missing translations. >>>>>> >>>>>> Thanks! >>>>>> ------------------------------ >>>>>> Click here to >>>>>> unsubscribe<[email protected]?body=SIGNOFF%20openmrs-devel-l>from >>>>>> OpenMRS Developers' mailing list >>>>> >>>>> >>>>> ------------------------------ >>>>> Click here to >>>>> unsubscribe<[email protected]?body=SIGNOFF%20openmrs-devel-l>from >>>>> OpenMRS Developers' mailing list >>>> >>>> >>>> >>> ------------------------------ >>> Click here to >>> unsubscribe<[email protected]?body=SIGNOFF%20openmrs-devel-l>from >>> OpenMRS Developers' mailing list >>> >> >> ------------------------------ >> Click here to >> unsubscribe<[email protected]?body=SIGNOFF%20openmrs-devel-l>from >> OpenMRS Developers' mailing list >> > > ------------------------------ > Click here to > unsubscribe<[email protected]?body=SIGNOFF%20openmrs-devel-l>from > OpenMRS Developers' mailing list > _________________________________________ 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]
