On 6 April 2011 21:11, mougeyc <[email protected]> wrote: > Hi, > > 3) Rewrite language.php file as an abstract script, and interface modules > for Apertium, Aspell and LanguageTool. > -> Separate the translation system and the environment management > system > -> Make the translation system as an PHP Object, which is initialised > with languages pairs > -> Extend the environment management system to allow writing of > interfaces modules for Aspell and LanguageTool
Proposing features that already exist is not much of a draw. Modularity for its own sake means nothing to the user. > -> Write these modules > > 4) Provide more formatting modules; currently only ODF, OOXML, html and > text are supported. Mediawiki (using apertium-mediawiki) and others are > wanted. > -> Add module for Rich Text Format formatting (using existing > Apertium's > modules) > There was a reason why the original formatting modules were not used (perhaps Arnaud can provide some detail here). It would be best to generate format handling from the same source as the usual format handlers. > Week3 : > More work hours are planned to make up for lost weeks. > > 4)(suite) -> Add module for Mediawiki formatting (using existing > Apertium's modules) > -> Make test for Pdf formatting, with pdf2html on a pdf set, and test > for > the reconstruction step > -> If they are inconclusive, write the pdf module > -> Provide a module using cuneiform ( who is able to recognize multiple > languages and maintain a basic layout ) for Pictures. The export HTML > functionality can be used (jointly with html module ). > Ooh... You had to go with Cuneiform? If you'd done more homework, you might have scored more points by going for Tesseract. (I'm half joking: I haven't done much recently, but I'm also a Tesseract developer; and half serious: Tesseract supports more of Apertium's core languages than Cuneiform does). > 8) Make it possible to input a TMX to help for a translation (either with > Apertium's TMX input system, or an external tool like OmegaT) > -> Ask Sergio Ortiz on the integration of TMX to identify and > translate segments from a translation memory Have you done that yet? > -> Make it > > > 9) Use existing server-side TMX database, so that the memory generated > after a > translation be stored and reused automatically for next translations > in > this language pair. (It might be wise to add some kind of validation > too, > to make sure that people don't mess with the whole system by > submitting > wrong translations...) > [snip] > 9)(continue and finish) > According to Jimmy O'Regan, it seems that it's a difficult task. Time is > needed. Let's be clear on what I'm talking about -- validation is hard, but there are some simple first steps you can take. I'd like you to be *much* more clear about /which/ kinds of validation you intend to perform. -- <Leftmost> jimregan, that's because deep inside you, you are evil. <Leftmost> Also not-so-deep inside you. ------------------------------------------------------------------------------ Xperia(TM) PLAY It's a major breakthrough. An authentic gaming smartphone on the nation's most reliable network. And it wants your games. http://p.sf.net/sfu/verizon-sfdev _______________________________________________ Apertium-stuff mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/apertium-stuff
