User:Littleowl/Littleowl pet - Revision history

Littleowl: removed user details

2016-06-30T09:22:19Z

removed user details

Show changes

Littleowl: /* Why Google and Apertium should sponsor it */

2010-04-16T10:01:32Z

Why Google and Apertium should sponsor it

Littleowl: /* Why Google and Apertium should sponsor it */ TMX

2010-04-16T09:51:09Z

Why Google and Apertium should sponsor it: TMX

Littleowl: /* Work plan */ review

2010-04-16T09:48:13Z

Work plan: review

Littleowl: /* Why Google and Apertium should sponsor it */ review

2010-04-16T09:41:20Z

Why Google and Apertium should sponsor it: review

Littleowl: /* References */

2010-04-16T00:07:57Z

References

Littleowl: /* Why Google and Apertium should sponsor it */

2010-04-16T00:07:27Z

Why Google and Apertium should sponsor it

Littleowl: /* Work plan */

2010-04-16T00:06:07Z

Work plan

Littleowl: /* How and who it will benefit in society */

2010-04-16T00:05:47Z

How and who it will benefit in society

Littleowl: /* How and who it will benefit in society */

2010-04-16T00:05:15Z

How and who it will benefit in society

@@ Line 54: / Line 54: @@
 # '''Disambiguation''': This is the case when Apertium engine gives us more than one alternative for a translated word. The ambiguity is incorporated in the translation flow by the POS tagger[7] which marks ambiguous words with an '=' symbol. Although this ambiguity does not reach now the output, it is possible to send this information to the output of the system. With this information in the system output, the tool would be able to provide definitions of these words on-the-fly from external resources. And let the user select the best option suggesting a default option and more alternatives in a hidden menu. Furthermore, two different sources can be used from Apertium: information for alternative translations generated through dixes[8] or information of homographs coded in the dictionaries but not available in the general Apertium translation flow.
 # '''Tracking/logging system''': It allows to save log information about operations done with the post-editing tool by user. It keeps track of disambiguation, word translation/replacement, deletion and edition by user. This feature will allow to improve Apertium translation system and its dictionaties extracting and analyzing the content of logged information. That information could also be used for user dictionaries and the integration with tools such as the project Tradubi[9] in the future.
-# '''Translation memory''': The post-editing tool will generate a translation memory in TMX[10] format using the already available Apertium tools for that purpose [11][12]. The translated memory will be generated from the original document sent to Apertium engine and the final post-edited text.
+# '''Translation memory generation''': The post-editing tool will generate a translation memory in TMX[10] format using the already available Apertium tools for that purpose [11][12]. The translated memory will be generated from the original document sent to Apertium engine and the final post-edited text.
 ==== How and who it will benefit in society ====

@@ Line 54: / Line 54: @@
 # '''Disambiguation''': This is the case when Apertium engine gives us more than one alternative for a translated word. The ambiguity is incorporated in the translation flow by the POS tagger[7] which marks ambiguous words with an '=' symbol. Although this ambiguity does not reach now the output, it is possible to send this information to the output of the system. With this information in the system output, the tool would be able to provide definitions of these words on-the-fly from external resources. And let the user select the best option suggesting a default option and more alternatives in a hidden menu. Furthermore, two different sources can be used from Apertium: information for alternative translations generated through dixes[8] or information of homographs coded in the dictionaries but not available in the general Apertium translation flow.
 # '''Tracking/logging system''': It allows to save log information about operations done with the post-editing tool by user. It keeps track of disambiguation, word translation/replacement, deletion and edition by user. This feature will allow to improve Apertium translation system and its dictionaties extracting and analyzing the content of logged information. That information could also be used for user dictionaries and the integration with tools such as the project Tradubi[9] in the future.
-# '''Translation memory''': The post-editing tool will generate a translation memory in TMX[10] format using the already available Apertium tools for that purpose [11][12].
+# '''Translation memory''': The post-editing tool will generate a translation memory in TMX[10] format using the already available Apertium tools for that purpose [11][12]. The translated memory will be generated from the original document sent to Apertium engine and the final post-edited text.
 ==== How and who it will benefit in society ====

@@ Line 82: / Line 82: @@
 <blockquote>
-Development of the Tracking/logging system (feature 4).
+Development of the Tracking/logging system (feature 4). Basicly user authentication and its structure. The tracking tokens will be fulfilled for each feature.
 </blockquote>
@@ Line 151: / Line 151: @@
 '''Project completed'''
-The Work plan above includes 60 hours of study, analysis and specification of the project. 60 hours to develop the core of the application. 120 hours to develop features and extent core functionalities. 60 hours of testing. And finally 60 hours of documentation. Every block includes periodic feedback with Apertium users and the mentor of the project in order to keep track of the project.
+The Work plan above includes 4 weeks of study during the bonding period, analysis and specification of the project. Another 4 weeks to develop the core of the application, its engine. Another 4 weeks to develop features and extent core functionalities. 2 weeks of testing. And finally 2 weeks of documentation. Every block includes periodic feedback with Apertium users and the mentor of the project in order to keep track of the project.
 === List your skills and give evidence of your qualifications ===

@@ Line 40: / Line 40: @@
 It is a tool to speed up revision of Apertium translations, therefore it will reduce the cost and time of many translations.
-From an existing web development/viewer[1] and web services[2] of Apertium project and also reusing an existing Open-Source WYSIWYG web-editor[3] replacing its functionality for the interface, the post-editing tool will provide the user with a series of features that will facilitate the post-editing of translated texts. Furthermore, the Apertium's community has a couple of web-based interfaces on PHP up and running so code could also be reused and even the Google Web Development Kit could also speed up the development.
+From an existing web development/viewer[1] and web services[2] of Apertium project or even reusing an existing Open-Source WYSIWYG web-editor[3] replacing its functionality for the interface, the post-editing tool will provide to the user a list of features that will facilitate the editing of translated texts. Furthermore, the Apertium's community has a couple of web-based interfaces on PHP up and running so code could also be reused and even the Google Web Development Kit could also speed up the development.
 The post-editing tool allows to translate texts and edit them before Apertium's reformatter using a graphic web-interface and the Apertium stream format[4]. This is possible using existing des-formatter and re-formatter tools within the Apertium project[5].
@@ Line 48: / Line 48: @@
 Once a text is translated and before Apertium's reformatter, there are still some issues in the translation which need manual edition with the post-editing tool. For example that is the case of untranslated words (absent from Apertium dictionaries) and ambiguity. Actually, Apertium optionally marks with a '*' words not found in Apertium dictionaries (unknown words) so they can be easily spotted in the resulting text. When there is no corresponding word for the target language, that word is kept the same way in the translation. Regarding ambiguity, Apertium offers the possibility of getting the list of alternative (due to ambiguity) translations in the output so the user can select the most appropriate alternative.
-The list of linguistic resources can be quite vast. Therefore I propose to focus the task in three language pairs (en<>sp, en<>ca and sp<>ca) and include the feedback from Apertium users and mentors in order to define and prioritise the list of features to be added. The initial list of features and linguistic resources of my proposal is the following:
+The list of linguistic resources can be quite vast. Therefore I propose to focus the task in three language pairs (en<>sp, en<>ca and sp<>ca) and to include the feedback from Apertium users and mentors in order to define and prioritize the list of features to be added. The initial list of features and linguistic resources of my proposal is the following:
 # '''Spell-checker''': Adding this feature in the post-editing tool the mistypings in the source language could be detected and easily corrected. In front of a misspelling in the source language, the tool provide suggestions not only in the source language but also in the target language using Apertium bilingual dictionaries.

@@ Line 179: / Line 179: @@
 [6] Apertium project. ''Using linguistic resources''. http://wiki.apertium.org/wiki/Using_linguistic_resources
-[7] Apertium project. ''Apertium-dixtools''. http://wiki.apertium.org/wiki/Apertium-dixtools
+[7] Apertium project. ''Tagger''. http://wiki.apertium.org/wiki/Tagger
-[8] Apertium project. ''Tagger''. http://wiki.apertium.org/wiki/Tagger
+[8] Apertium project. ''Apertium-dixtools''. http://wiki.apertium.org/wiki/Apertium-dixtools
 [9] Tradubi project. ''Tradubi''. http://www.tradubi.com

@@ Line 91: / Line 91: @@
 </blockquote>
-* '''Week 4''': Refine and bug fixing of the Post-edition tool engine
+* '''Week 4''': Refine and bug fixing of the Post-editing tool engine
 <blockquote>

@@ Line 58: / Line 58: @@
 ==== How and who it will benefit in society ====
-After translating with Apertium revision work has to be done to consider a translation as an "adequate" translation. An intelligent post-editing environment will help doing this task. In this environment some typical mistakes in the translation process that can be automatically detected (for example unknown words and homographs) could be highlighted to be taken in consideration while doing post-edition. Some typical mistakes could also be defined to advise the post-editor to check them.
+After translating with Apertium revision work has to be done to consider a translation as an "adequate" translation. An intelligent post-editing environment will help doing this task. In this environment some typical mistakes in the translation process that can be automatically detected (for example unknown words and homographs) could be highlighted to be taken in consideration while doing post-editing. Some typical mistakes could also be defined to advise the post-editor to check them.
 ==== Work plan ====