Difference between revisions of "SOCR Internationalization Project"

From SOCR
Jump to: navigation, search
m
 
m
 
(3 intermediate revisions by the same user not shown)
Line 1: Line 1:
==[[SOCR]] Project - [[SOCR]] Internationalization Project==
+
==[[Available_SOCR_Development_Projects | SOCR Project]] - [[SOCR]] Internationalization Project==
  
* '''Project Goal''': To develop a clever, extensible and light-weight approach for accurate machine translation of all [[SOCR]] resources (course and general educational materials - notes, assignments, solutions, forums, etc.; Wiki activities; applet contents; etc.) This multi-lingual [[SOCR]] support should be seamless, just like this wiki project page translation on the bottom, however, it should expand on the available languages, type of resource translation, allow easy extension and require low maintanance.
+
* '''Project Goal''': To develop a clever, extensible and light-weight approach for accurate machine translation of all [[SOCR]] resources (course and general educational materials - notes, assignments, solutions, forums, etc.; Wiki activities; applet contents; etc.) This multi-lingual [[SOCR]] support should be seamless, just like this Wiki project page translation on the bottom, however, it should expand on the available languages, type of resource translation, allow easy extension and require low maintenance.
  
  
* '''Background''': Research the all types of ([[SOCR]] materials first. These include course and general educational materials - notes ([http://www.stat.ucla.edu/%7Edinov/courses_students.dir/06/Fall/STAT13.1.dir/STAT13_notes.html e.g.]), assignments ([http://www.stat.ucla.edu/%7Edinov/courses_students.dir/06/Fall/STAT13.1.dir/assignments.html e.g.]), data ([http://www.stat.ucla.edu/%7Edinov/courses_students.dir/06/Fall/DataFiles/Chpt%201/Hotdogs.html e.g.]), solutions ([http://www.stat.ucla.edu/%7Edinov/courses_students.dir/06/Fall/STAT13.1.dir/assignments.html e.g.]), forums ([http://moodle.stat.ucla.edu/mod/forum/view.php?f=159 e.g.]), etc.; Wiki activities ([http://wiki.stat.ucla.edu/socr/index.php/SOCR_EduMaterials e.g.]); applet contents ([http://www.socr.ucla.edu/htmls/SOCR_Distributions.html e.g.]); etc.
+
* '''Background''': Research the all types of [[SOCR]] materials first. These include course and general educational materials - notes ([http://www.stat.ucla.edu/%7Edinov/courses_students.dir/06/Fall/STAT13.1.dir/STAT13_notes.html e.g.]), assignments ([http://www.stat.ucla.edu/%7Edinov/courses_students.dir/06/Fall/STAT13.1.dir/assignments.html e.g.]), data ([http://www.stat.ucla.edu/%7Edinov/courses_students.dir/06/Fall/DataFiles/Chpt%201/Hotdogs.html e.g.]), solutions ([http://www.stat.ucla.edu/%7Edinov/courses_students.dir/06/Fall/STAT13.1.dir/assignments.html e.g.]), forums ([http://moodle.stat.ucla.edu/mod/forum/view.php?f=159 e.g.]), etc.; Wiki activities ([http://wiki.stat.ucla.edu/socr/index.php/SOCR_EduMaterials e.g.]); applet contents ([http://www.socr.ucla.edu/htmls/SOCR_Distributions.html e.g.]); etc. Then research all available machine language translations, tools, resources, web-services, etc. <br>This is '''not''' a project to develop a new multi-lingual machine translation of web content. This is a project that should utilize existent technology and translation tools developed by others, that do not only translate word-for-word, but rather use advanced computational algorithms, language syntax and grammar to provide to the end-user all English-based [[SOCR]] materials in as many languages as possible. This framework should be easy to update and revise - for example if better translators for certain languages become available, a single URL change in a core structure will automatically make the new translators available to all [[SOCR]] materials (this should not require changes in all [[SOCR]] pages or other resources!)
  
* '''The basic Use-Case''':
+
 
** User starts (a new) applet (SOCR_R_Analyses.html). The applet establishes a secure connection with Java/C/JNI server and retrieves the (plug-ins) for all R-analyses that we have described (see for example how we do the SOCR Analyses: [http://socr.ucla.edu/htmls/jars/implementedAnalysis.txt implementedAnalysis.txt]).
+
* '''Project specs''':
** Then the Java client GUI displays a drop-down list of these (the way we do the standard SOCR Java analyses, for example) and allows the user to get help (R-help + Wikipedia help) on each type of analysis. Once the user selects an analysis, they are allowed to enter data, simulate data or paste in their own data – the way the Java SOCR analyses do.
+
** The proposed [[SOCR]] Internationalization Framework should include a core Hash-map between languages and translators (tools). This mapping may be in XML or TXT format and allow easy updating.
** The SOCR Java GUI interface will need to configure itself according to the type of analysis selected by the user to allow full control of the parameters that go in any R-analysis that we “describe”. Looking over at JGR/RJava and other such initiatives may be helpful. Once the user selects all appropriate parameters and enters their data the Client submits the job to the SOCR_R_Server, who executes the task and returns the results back to the client. The client may then display the results in a new “Results” tab-pane under the specific analysis GUI. Note that R results could be numeric, graphical, textual. Also, error and return codes from R should be gracefully handled (reported to the user the way R does and point the user to the specific online R docs that discuss the specific type of error.
+
** There should be interfaces that parse this language/tool mapping and provide specific functionalities to the various [[SOCR]] resources that need to be translated.
 +
** The translator tools may be online URL translators, web-services or other novel technologies to delegating the language translation tasks to.
  
 
===[[Available_SOCR_Development_Projects]]===
 
===[[Available_SOCR_Development_Projects]]===
Line 17: Line 18:
  
 
<hr>
 
<hr>
*[http://socr.stat.ucla.edu/docs/index.html SOCR JavaDoc]
+
*[http://socr.stat.ucla.edu/docs/index.html SOCR JavaDoc]
  
 
{{translate|pageName=http://wiki.stat.ucla.edu/socr/index.php?title=SOCR_Internationalization_Project}}
 
{{translate|pageName=http://wiki.stat.ucla.edu/socr/index.php?title=SOCR_Internationalization_Project}}

Latest revision as of 15:01, 8 December 2009

SOCR Project - SOCR Internationalization Project

  • Project Goal: To develop a clever, extensible and light-weight approach for accurate machine translation of all SOCR resources (course and general educational materials - notes, assignments, solutions, forums, etc.; Wiki activities; applet contents; etc.) This multi-lingual SOCR support should be seamless, just like this Wiki project page translation on the bottom, however, it should expand on the available languages, type of resource translation, allow easy extension and require low maintenance.


  • Background: Research the all types of SOCR materials first. These include course and general educational materials - notes (e.g.), assignments (e.g.), data (e.g.), solutions (e.g.), forums (e.g.), etc.; Wiki activities (e.g.); applet contents (e.g.); etc. Then research all available machine language translations, tools, resources, web-services, etc.
    This is not a project to develop a new multi-lingual machine translation of web content. This is a project that should utilize existent technology and translation tools developed by others, that do not only translate word-for-word, but rather use advanced computational algorithms, language syntax and grammar to provide to the end-user all English-based SOCR materials in as many languages as possible. This framework should be easy to update and revise - for example if better translators for certain languages become available, a single URL change in a core structure will automatically make the new translators available to all SOCR materials (this should not require changes in all SOCR pages or other resources!)


  • Project specs:
    • The proposed SOCR Internationalization Framework should include a core Hash-map between languages and translators (tools). This mapping may be in XML or TXT format and allow easy updating.
    • There should be interfaces that parse this language/tool mapping and provide specific functionalities to the various SOCR resources that need to be translated.
    • The translator tools may be online URL translators, web-services or other novel technologies to delegating the language translation tasks to.

Available_SOCR_Development_Projects

SOCR_ProposalSubmissionGuidelines




Translate this page:

(default)
Uk flag.gif

Deutsch
De flag.gif

Español
Es flag.gif

Français
Fr flag.gif

Italiano
It flag.gif

Português
Pt flag.gif

日本語
Jp flag.gif

България
Bg flag.gif

الامارات العربية المتحدة
Ae flag.gif

Suomi
Fi flag.gif

इस भाषा में
In flag.gif

Norge
No flag.png

한국어
Kr flag.gif

中文
Cn flag.gif

繁体中文
Cn flag.gif

Русский
Ru flag.gif

Nederlands
Nl flag.gif

Ελληνικά
Gr flag.gif

Hrvatska
Hr flag.gif

Česká republika
Cz flag.gif

Danmark
Dk flag.gif

Polska
Pl flag.png

România
Ro flag.png

Sverige
Se flag.gif