Hi there, >> 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. Actually, I was the one to suggest working a little bit on modularity. I does not matter for the end user, but the objective if for the people who will install the interface to be able to enable / disable features easily. For example, some people may not care about the logging module, which is costly in terms of performance and a great source of bugs or browser incompatibilities : if the code was modular enough for it to be disabled easily, it would be a progress.
>> -> 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. Well, I had to partly rewrite the modules mostly because apertium didn't really provide formatting commands (apertium-unformat was here, but there was no command to rebuild the document afterwards). All was taken care of in the apertium main script, which did unformatting -> translation -> reformatting at once. Since I needed to pause at the translation step, I had to rewrite parts of it myself : specifically, the unzipping of odt and docx documents. But I did rely on the apertium-des* and apertium-re* commands to escape formatting information in the included xml files. I'd advise a similar approach here : the apertium-des* and apertium-re* work with raw text files; "unpacking" tasks should probably be done in the php script, and the contents should then be passed to the corresponding apertium-des* command (and run the opposite process after translation). Best, Arnaud ------------------------------------------------------------------------------ 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
