Simple Localization System

If you have worked with localizing Java stuff or Firefox extensions, or anything similar, you already dealt with property files (tokens to text mapping), and this is admittedly not new as explained in the article. What seems to be advocated as new are the following:

• central server to pull translations from (this is getting to be in production form by brmassa already in Drupal: http://groups.drupal.org/node/4258)
• in place translation on the site, to give context (Konstantin had this on his Google Summer of Code 2006(!) project, but he did not complete this one as it seems from the results: http://cvs.drupal.org/viewcvs/drupal/contributions/sandbox/timcn/soc/liv...)

So this does not seem to be new. In fact using property files offers you less tooling support then using Gettext stuff, you can only see one text version at a time (the one you are writing at the moment, by looking at the token only). Drupal does not use tokens so that the site works out of the box without the locale module overhead, and this does include the disadvantage that there is really no context of strings, so if you translate some stuff on the imaginary in place web interface, that same string might appear on other parts of the site, so the context you translated that in might not be the only one.

So to adapt SLS, we would need to convert to using tokens instead of strings, enforce the overhead of locale module (or a new locale module replacement) on all sites, English or not. Then deal with a less translation friendly file format which might have web based tooling support or not at that time (maybe we need to develop our own), so that you cannot work with the files on the file level, you always need the tool.

Is this the next big thing? :)

BTW I also commented on the possible controllability problems of the live translation update solution on the node linked above, which makes it a shaky choice for serious web sites, although it still is a very attractive solution for hobby sites, where tight control of the interface translations is not a requirement.

Project name : GUI add multi language
Project description :
การใช้งานเวปไชค์มในแต่ละประเทศมีความแตกต่างกันในด้านของภาษาในการทำงานของ Multi language นั้นจะทำให้การใช้งานและการเข้าใจในการติดต่อสื่อสารลายละเอียดให้เข้าใจเป็นความหมายเดียวกันและทำให้สะดวกในการใช้งานเวปมากขึ้น โดยตัวโปรแกรมจะมี mode Edit เพื่อทำการเพิ่มคำใหม่ๆลงในตัวเก็บภาษา เพื่อทำการแก้ไขตัวเวปได้ทันที และเมื่อต้องการใช้งานแบบภาษาตามเดิม เราก็สามารถเปลี่ยนกลับไปเป็นโหมดเดิมได้ โดยการเลือกในช่องเลือกภาษาตามที่ต้องการ
Over view
I'll add multi language by use I18N for drupal6.1 plus GUI for add multilanguage and multi selection use language in web. Use by Edit mode .when you entry in edit mode you can edit language and save you language but if you want it back you just can choose the “droupdown list” and change other language do you want.

Implementation details:

Java Script and PHP

Resource:
http://groups.drupal.org/i18n

My Profile:
Name : keattikun
Lastname: sittiyoth(Oxygenerror)
E-Mail :Oxygenerror@hotmail.com
Age: 23

benefit to drupal community
schedule/timeline