Re: [Slashcode-development] i18n slashcode

[Shuji S. <sa...@li...>]

Moin, 

Brian Aker <br...@ta...> wrote:

> Shuji Sado wrote:
> > Is there the plan that Slashcode will be internationalized (or localized
> > non-english)?  If the plan exists, I want the load map and code.
> It is a wish, but not the highest priority. In theory at the moment
> you could take the slashcode theme in bender and convert it to
> Japanese. I'm not sure what you might find that we didn't consider,
> but we would happily take patches for it.

Oh, wish...

At first, I describe only Japanaize.  A problem in Japanese support
is charset handling.  Three charset(Shift JIS, ISO-2022-JP, EUC-JP)
are used generally in Japan, and a Japanaized system needs to handling
these charset simultaneously.  In other words, Japanese user will use
three charset, but must handle it with Slashcode.  And charset
conversion becomes necessary because web document is not made to
coexist with different charset.

Korean, Chinese and Eastern European languages..., I do not understand
it about these language.  However, these language support will be
possible if charset conversion of input strings to text-area is enabled.

Last month, I asked Larry Wall about Unicode(utf8) support facility
of Perl5.6. (He visited Japan as keynote speaker of LinuxConfrence
2000 Fall, and I was a chairman of the conference.)  He says,
the string functions supports utf8 character, but other facility
is not implemented.  If there is not facility of charset conversion,
i18n of Slashcode is impossible.


Text::Iconv module (wrapper of glibc iconv ?) exist in CPAN, but
this module cannot get charset name. Then it is not enough in
Japanization, but it may advance in Internationalization.


Fummm... I intend to work about "Japanization". It may take time.

---
Shuji Sado
 Japan Linux Association  Executive Director (sa...@li...)
 Open Source Group Japan  President (sa...@op...)
 VA Linux Systems Japan K.K. (sa...@va...)