> > El dc 30 de 03 de 2011 a les 11:05 -0300, en/na Lautenai Jr. va > escriure: > > Hi, my name is Lautenai and I am from Brazil. I?m PhD candidate in > > Translation Studies at Universidade Federal de Santa Catarina. > > > > My background is based on translation and technology. My skills are > > PHP, MySQL and Javascript. > > Since last year my interest is on the development of a translation > > interface for Apertium Translator. Now, the purpose is to continue the > > development started by Arnauld. > > My ideas are: > > Create a translation work-flow for post editing task; > > Redesign the web interface by using AJAX based on Jquery focusing on > > usability; > > Use a PHP Framework to increase the modularity of the code and > > reusability (I?ve been using Codeigniter for my projects); > > Use Jquery Javascript Framework to improve the cross-browser > > compatibility; > > Improve Logging Feature; > > Integrate tools like After The Deadline (a great tool for checking > > text) )using Jquery API and others for a better quality in > > translations; > > Improve Search&Replace; > > Export to TMX and Wordfast; > > Provide a feature to localise the interface;Provide an > > easy-installation through a web interface; > > Use Apertium as a web service to get translations (maybe through POST > > and GET); > > > > Maybe this idea could to create a Translator Workbench... > > Please let me know what do you think. > > Cool, did you manage to install it ?
If people or organizations want to install on their own server, they just need to copy files to server, setup PHP and MysSQL and can use. > What features were you thinking > about for the "work flow" ? Instead of having all text in a text area, the text could be spitted into sentences and then translate sentence by sentence (maybe using a sliding feature). For more information and context about each sentence a show context feature could be added. Mark each sentence as translated, reviewed or approved to have a quality control of each sentence. Provide a progress of translation based on that criteria. These are some ideas I have in mind. > How were you thinking of handling it ? > There are two ways of handling it: (i) user auth; (ii) user session. In first case, this app could be used as an workbench and all users can have accounts and store all their own translation. I second case, it could generate e session code and save in database with all translation units and users can have access at any time with that session code. On 30 March 2011 15:05, Lautenai Jr. <[email protected]> wrote: > > Improve Logging Feature; > > Logging is (IMO) the most interesting part of AWI. Could you provide > some more detail? Any change to each translation unit (TU) could be stored in the database. Information about time and other important thing could be stored too. A revision history feature also can be added. Using revision history feature all changes could be highlighted in each TU. In case when users have accounts and share their translation projects, logging could be used to show what and who have been changed. Just some thoughts about logging feature. > > Export to TMX and Wordfast; > > It already supports TMX export, though that could, perhaps, be > improved. Wordfast export should not be necessary - Wordfast can > import TMX, the format is trivial, and I think we'd prefer not to > encourage the use of proprietary tools and formats. Sorry about wordfast, I forget it imports TMX files as well. ;)
------------------------------------------------------------------------------ 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
