Browser based software translation: Difference between revisions

From OLPC
Jump to navigation Jump to search
 
(4 intermediate revisions by 4 users not shown)
Line 18: Line 18:
technical part of application translation
technical part of application translation


== Prototyp ==
== Prototype ==
Hier is a prototyp how browser based translation could work:
Here is a prototype showing how browser-based translation could work:


=== features ===
=== features ===
Line 50: Line 50:
[[Category:Language support]]
[[Category:Language support]]
[[Category:Languages (international)]]
[[Category:Languages (international)]]
{{merge}}
{{merge|localization}}

Latest revision as of 19:37, 8 November 2010

OLPC will be introduced in countries with languages that are not supported by linux, windows and co. Software and documentation translation is a big task.

Other translation software

Recommended by olpc:

http://translate.sourceforge.net/

This seems to be very similar: Rosetta is a Web-based system for translating open source software into any language.

https://launchpad.net/rosetta

Programing skills vs. language skills

Some people know human languages but are not able to do the technical part of application translation

Prototype

Here is a prototype showing how browser-based translation could work:

features

  • edit all strings
  • UTF-8
  • download of changed language file


PSI Jabber Client

Webform

http://lamp2.fh-stpoelten.ac.at/~lbz/beispiele/ss2006/olpc/translate/site.php

The webapplications source code

http://lamp2.fh-stpoelten.ac.at/~lbz/beispiele/ss2006/olpc/translate/site.phps (~40 lines) http://lamp2.fh-stpoelten.ac.at/~lbz/beispiele/ss2006/olpc/translate/trans.xslt (~65 lines)


PSI language packs

http://psi-im.org/download

ToDo

  • Version management
  • Support for more languages
  • Support for more applications
Merge-arrows.gif
It has been suggested that this article or section be merged with localization. (Discuss)