Yeah, I noticed those lines the other day, too. For all intents and
purposes, where Japanese (LANG_JA/ja_JP) has code, Korean (LANG_KO/ko_KR)
should, too, but Korean is missing in that section and it works just fine.
It might be necessary under certain platforms or conditions, though... I
just know it works when I use it (Linux, mostly, but sometimes Windows.)
-Mark
On Wed, 21 Jul 2004, Karl Ove Hufthammer wrote:
> What does these lines in tuxpaint.c do:
>
> if (language == LANG_JA)
> {
> putenv("OUTPUT_CHARSET=ja_JP.UTF-8");
> }
> else if (language == LANG_HE)
> {
> putenv("OUTPUT_CHARSET=he_IL");
> convert_open("ISO8859-8");
> }
> else if (language == LANG_PL)
> {
> putenv("OUTPUT_CHARSET=pl_PL.UTF-8");
> convert_open("ISO8859-2");
> }
> ...
>
> --
> Karl Ove Hufthammer
> _______________________________________________
> Tuxpaint-dev mailing list
> [EMAIL PROTECTED]
> http://tux4kids.net/mailman/listinfo/tuxpaint-dev
>
--
Mark K. Kim
AIM: markus kimius
Homepage: http://www.cbreak.org/
Xanga: http://www.xanga.com/vindaci
Friendster: http://www.friendster.com/user.php?uid=13046
PGP key fingerprint: 7324 BACA 53AD E504 A76E 5167 6822 94F0 F298 5DCE
PGP key available on the homepage
_______________________________________________
Tuxpaint-dev mailing list
[EMAIL PROTECTED]
http://tux4kids.net/mailman/listinfo/tuxpaint-dev
