Browser based software translation: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
|||
Line 10: | Line 10: | ||
== Prototyp == |
== Prototyp == |
||
Hier is a prototyp how browser based translation could work: |
Hier is a prototyp how browser based translation could work: |
||
=== features === |
|||
*edit all strings |
|||
*UTF-8 |
|||
*download of changed language file |
|||
=== PSI Jabber Client === |
=== PSI Jabber Client === |
Revision as of 20:38, 22 May 2006
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.
Programing skills vs. language skills
Some people know human languages but are not able to do the technical part of application translation
Prototyp
Hier is a prototyp 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
ToDo
- Version management
- Support for more languages
- Support for more applications