On 1 April 2011 14:52, mougeyc <[email protected]> wrote: > 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 Mediawiki formatting > -> Add module for Rich Text Format formatting > -> Add module for Pdf formatting
How do you propose to handle pdf? > -> Perhaps consider the possibility of using OCR for Pictures ( by > using > Google Apis for example, or OpenCV which is open source ) > OpenCV? You mean, you propose to build your own OCR system? It would be more realistic to use Tesseract, Cuneiform, OCROpus, or gOCR. > 5) Localisation, make it possible to translate the interface into > different languages. > -> The localisation is given by IP Address, or by the browser, or set > by > the user Wrong order. Browser first. Users know which language they speak, IP-based lookups make sweeping assumptions. > -> The choice is save ( cookies, .. ) > -> The interface texts are load from XML files, which contain the text > for every button, checkbox, ... > -> Perhaps allow the user to propose new interface text ( by making XML > file ), or using his own > A configurable UI might be nice, but make it optional. > 6) Improve overall design > -> The current design is very basic ( or non-existent ) > -> The Apertium website will pass on WordPress system, so the overall > design can be taken > -> If the website isn't yet on WordPress, make a design similar to the > Apertium current website ( in colour, simplicity, .. ) > > 7) Fix possibly remaining bugs > -> It's a task on the long time, but at this stage, I want to make a > complete test of the system > -> It's include : > - Fix remaining bugs > - Make some test sets > - Optimize code > - Fix security issues > > 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) ; By the way, > familiarize with TMX format There is a community bonding period, in which you are to get familiar with the people and technologies you'll be working with: remove 'By the way, familiarize with TMX format'. > 9) Design a 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...) I think you don't appreciate how difficult that is - Google have quite a long section in one of their patents describing such a system. It might just be best to provide a mechanism to allow LanguageTool's bitext checking to be used, and leave the details to others. > -> These tasks go together : The main idea is to permit to the user to > give or alter current translations, export them to TMX format. At the same > time, these modifications are saved in a server-side TMX database, which > contain two kinds of dictionaries by language : > - Submitted and awaiting for approving translations > - Approved translations > -> Add in the user interface the possibility to use Submitted and > awaiting for approving translations ( not recommended ) and/or approved > translations ( recommended ) > -> May we can see here a way to use the logging system > > 10) Provide a module to use the apertium.org web service instead of a > local Apertium installation > -> Make a bridge between apertium.org website and local Apertium > installation, perhaps by parsing code result ( simulate the entry of user > on the website, and analyse the result ) but it use pregmatch => expensive, > or perhaps by writing an API for the apertium.org web-service, which will > avoid the phase return analysis What? > -> Add the possibility for the user to use this service, in the > interface > > 11) Fix new or remaining s bugs > -> Stand back, redo 7) > > 12) Make it faster and cross-browser compatible > -> Give, and add to JS existing modules, libraries to adapt the system > for recent browser. We can down to IE 6. > -> Make it faster by analysing the time critical path > -> Make the different libraries download faster, by reducing their > size ( > like Google for jquery ) > > 13) Make installation easier. Fully describe the installation process on > the Wiki. > -> Add screen-shot/video tutorial to the Wiki to describe the > installation. > -> For Debian based system, may create a *.deb package, *.rpm for Red > hat, .. > -> Perhaps create a simple interface for the installation process ( > more > attractive for Ms Michu ) Ms Michu? > > 14) Improve integration with Wikipedia — it should be able to fetch pages, > translate, allow to be revised and then published. > -> Integrate module for recognize Wikipedia format > -> Make or use existing Wikipedia API to fetch pages, and post them ( > allow to be revised and then published ) > See http://www.wikibhasha.org/ > 15) Provide modules to integrate alternative tools for spell and grammar > checking (AfterTheDeadline, etc.) > -> Make outputs during the translation process, which can be redirected > to others tool > -> Define the possible interaction with the software > -> Implement these interactions > > > Find a way to extract useful information from the dynamic event logging is > a reflexion on all the summer. > Ideas : > -> Statistics > -> Auto-completion > -> Make current dictionaries better ( 8) 9) ) > -> Propose text correction ( like a Google research ) What? Do you mean, by using a Markov chain generator, like Google Scribe? -- <Leftmost> jimregan, that's because deep inside you, you are evil. <Leftmost> Also not-so-deep inside you. ------------------------------------------------------------------------------ Create and publish websites with WebMatrix Use the most popular FREE web apps or write code yourself; WebMatrix provides all the features you need to develop and publish your website. http://p.sf.net/sfu/ms-webmatrix-sf _______________________________________________ Apertium-stuff mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/apertium-stuff
