Hi there, if the Apertium OmegaT plugin has not been modified since it was contributed, there is a task that a Java programmer could probably attempt with a bit of help from some of our Java experts: escaping OmegaT's format codes (<u>, <i1>, etc.) so that Apertium does not translate them. This involves: researching a bit what kind of format tags OmegaT produces (I can help here), and writing a quick filter that does that. Would this be an adequate GCI task? It looks like a quick hack to me, but requires a bit of guidance.
What do you guys think? Mikel On 22/10/12 21:14, Jimmy O'Regan wrote: > http://wiki.apertium.org/wiki/Task_ideas_for_Google_Code-in > > Feel free to add tasks - we now have the minimum 5 tasks in each > category, but more are welcome. Please bear in mind that these are > intended to be completed by high school students. > -- Mikel L. Forcada (http://www.dlsi.ua.es/~mlf/) Departament de Llenguatges i Sistemes Informàtics Universitat d'Alacant E-03071 Alacant, Spain Phone: +34 96 590 9776 Fax: +34 96 590 9326 ------------------------------------------------------------------------------ Everyone hates slow websites. So do we. Make your web apps faster with AppDynamics Download AppDynamics Lite for free today: http://p.sf.net/sfu/appdyn_sfd2d_oct _______________________________________________ Apertium-stuff mailing list Apertium-stuff@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/apertium-stuff
