From: Junio C Hamano <gitster@pobox.com>
Date: Sat, 23 May 2009 01:02:09 GMT
Subject: Re: [PATCH 2/2] t8005: convert CP1251 character set to ISO8859-5
Message-ID: <7vskiw4ooe.fsf@alter.siamese.dyndns.org>
In-Reply-To: <p2A1PR1KFf_G_uMMwQZtVXPPBSNcQqEAV1ZnkoQLMJaPzWwJrkH_HCs5Kbt70yQlltZJxs4WxXo@cipher.nrlssc.navy.mil>

Brandon Casey <casey@nrlssc.navy.mil> writes:

> This should still provide the same breadth of testing: a russian code set,
> a japanese code set, and unicode.  Wikipedia says that ISO8859-5 is not
> as commonly used as either CP1251 or KOI8-R, but it is available on these
> old platforms.  You'd think that if Solaris 7 has it _and_ IRIX has it,
> then everything else would too, but still feel free to drop this anyway.
> Neither of those platforms, or Solaris 10 (for me) can convert between
> any of the russian and japanese encodings, so t8005.[23] still fail, and I
> doubt there is any hope.

Thanks.

My earlier experience with Sun is that their iconv cannot convert between
different encodings of Japanese but can use UTF-8 as a pivot to convert,
e.g. SJIS -> UTF-8 -> ISO-2022.  Perhaps there is an workaround, but I
dunno.