Thai translation

With a translation resource contributed by Pladao Office project,
now available freely in a coming OO.o 1.1.2 (branch srx645). Currently kept here.

We may able to start an indepedently, pooled, translation project for
Which may utilized by any party.
OfficeTLE, Pladao Office, Thai localized build, for concrete examples.

“Different offerings and features. One Thai language.”

One benefit from this, at least, is to minimize the training cost,
also learning curve to switch between those OOo-based suites.

In Thai IT book market right now,
Pladao Office is unarguably the most popular suite.
If OfficeTLE, and also any other OOo-based suites,
use the UI texts based on what Pladao Office has contributed,
obviously, they will got the benefit.

Actually, everybody wins.

The key is, Pladao Office project contributors (mainly from Sun and Algorithms),
should also change their translations’ destination to here, the newly established pool.

Method (Technical)

One productive way to do that, is by web collaboration.
A proposed method is,

1) Convert OOo GSI to the universal po files (recognized by GNU gettext).
Using Translate.

2.1) For offline translation,
we may use gtranslator, or KBabel.

2.2) For online translation (preferred),
we may use the project proposed by kitty.
(The original initiative may be that one pioneered by korakot, the thai-po central project.
Anyway, the project was ‘abandoned’ for some times.)

(Actually, we may go with OO.o’s GSI format.
Using tools like GSI Translator (offline) or OOo webtranslation (online).
But those tools are, in my opinion, not solid yet.
So I preferred to go with the “standard” format like po.
The reason is very obvious, we can leverage many existing good po tools.)

The rest will follow the model of GNOME Thai Translation project.

Update: Preferrably, the translations should conform with a glossary from OpenTLE.

more details to come.

Leave a Reply

This site uses Akismet to reduce spam. Learn how your comment data is processed.