Multi - Language Support

Coool

Joined: 2002-09-18
Posts: 4

Posted: Sat, 2002-09-21 15:36

I'm interesting in multi - language support for Gallery. I think its not so difficult to do. I do it myself, but I must do it every time, when i upgrade it. It just take my time. I'll be thankful if you do that. Because then multi - language support for Gallery will be standart for this Open Source project. Thank's.

photon

Joined: 2002-09-24
Posts: 5

Posted: Tue, 2002-09-24 00:36

Could you elaborate a bit what you meant by multi-language support?
Did you mean L10N(localization) or I18N(internationalization)?
L10N involves translating menus and messages while I18N is geared
toward making it 'speak multiple languages at a time'.
In a sense, it's trivial to make Gallery multilingual with Apache
server. Simply adding the following directive to the apache
configuration file will enable Gallery to accept and render comments
in many different languages for a single photo.

<directory /gallery>
AddDefaultCharset UTF-8
</directory>

Most modern browsers have no problem with UTF-8 and
UTF-8 is the only ASCII compatible encoding that can
represent a wide range of languages (virtually all of them).

Using UTF-8 across the board significantly simplifies
L10N as well. Suppose Gallery is localized for
Japanese and Shift_JIS is used for Japanese UI/menu.
Then, it's __impossible__ to have album names, album
description, album title, comments in French, Russian,
and Korean. With UTF-8, what language can
be used in those places is totally independent
of the UI language (in this case, Japanese). This is
how web browsers like Mozilla and MS IE are
written and work. Everything is taken care of
internally in Unicode and even externally Unicode
is used in all possible cases.

PHP 4.x offers a couple of new functions to facilate
this along with a family of gettext() related functions.
They're bind_textdomain_codeset() and
iconv(). I used them to I18Nize horde/IMP
(http://www.horde.org). horde/IMP had been
localized in over 10 languages, but it was not
I18Nized properly, but with two new functions,
I was able to do that.

Coool

Joined: 2002-09-18
Posts: 4

Posted: Wed, 2002-09-25 07:08

I mean to make translation for other languages... like in postnuke or php-nuke... But thank's anyway for help. :wink:

Coool Joined: 2002-09-18 Posts: 4	Posted: Sat, 2002-09-21 15:36
	I'm interesting in multi - language support for Gallery. I think its not so difficult to do. I do it myself, but I must do it every time, when i upgrade it. It just take my time. I'll be thankful if you do that. Because then multi - language support for Gallery will be standart for this Open Source project. Thank's.
	XUser login Username: * Password: * Create new account Request new password
photon Joined: 2002-09-24 Posts: 5	Posted: Tue, 2002-09-24 00:36
	Could you elaborate a bit what you meant by multi-language support? Did you mean L10N(localization) or I18N(internationalization)? L10N involves translating menus and messages while I18N is geared toward making it 'speak multiple languages at a time'. In a sense, it's trivial to make Gallery multilingual with Apache server. Simply adding the following directive to the apache configuration file will enable Gallery to accept and render comments in many different languages for a single photo. <directory /gallery> AddDefaultCharset UTF-8 </directory> Most modern browsers have no problem with UTF-8 and UTF-8 is the only ASCII compatible encoding that can represent a wide range of languages (virtually all of them). Using UTF-8 across the board significantly simplifies L10N as well. Suppose Gallery is localized for Japanese and Shift_JIS is used for Japanese UI/menu. Then, it's __impossible__ to have album names, album description, album title, comments in French, Russian, and Korean. With UTF-8, what language can be used in those places is totally independent of the UI language (in this case, Japanese). This is how web browsers like Mozilla and MS IE are written and work. Everything is taken care of internally in Unicode and even externally Unicode is used in all possible cases. PHP 4.x offers a couple of new functions to facilate this along with a family of gettext() related functions. They're bind_textdomain_codeset() and iconv(). I used them to I18Nize horde/IMP (http://www.horde.org). horde/IMP had been localized in over 10 languages, but it was not I18Nized properly, but with two new functions, I was able to do that.

Coool Joined: 2002-09-18 Posts: 4	Posted: Wed, 2002-09-25 07:08
	I mean to make translation for other languages... like in postnuke or php-nuke... But thank's anyway for help. :wink:

Multi - Language Support

XUser login