All of lore.kernel.org
 help / color / mirror / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: Brandon Casey <casey@nrlssc.navy.mil>
Cc: git@vger.kernel.org
Subject: Re: [PATCH 2/2] t8005: convert CP1251 character set to ISO8859-5
Date: Fri, 22 May 2009 18:02:09 -0700	[thread overview]
Message-ID: <7vskiw4ooe.fsf@alter.siamese.dyndns.org> (raw)
In-Reply-To: <p2A1PR1KFf_G_uMMwQZtVXPPBSNcQqEAV1ZnkoQLMJaPzWwJrkH_HCs5Kbt70yQlltZJxs4WxXo@cipher.nrlssc.navy.mil> (Brandon Casey's message of "Fri\, 22 May 2009 18\:47\:06 -0500")

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.

  reply	other threads:[~2009-05-23  1:02 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-05-22 15:25 [PATCH] t8005: use more portable character encoding names Brandon Casey
2009-05-22 16:22 ` Junio C Hamano
2009-05-22 16:51   ` Brandon Casey
2009-05-22 23:04   ` Alex Riesen
2009-05-22 23:47   ` [PATCH 1/2] " Brandon Casey
2009-05-22 23:47     ` [PATCH 2/2] t8005: convert CP1251 character set to ISO8859-5 Brandon Casey
2009-05-23  1:02       ` Junio C Hamano [this message]
2009-05-23  1:06         ` Junio C Hamano
2009-05-25  9:20           ` Jeff King
2009-05-25  9:26             ` Jeff King
2009-05-26 14:56             ` Brandon Casey
2009-05-28 18:43               ` Jeff King
2009-05-26 14:57             ` Brandon Casey
2009-05-28 18:47               ` Jeff King
2009-05-26 22:56             ` Junio C Hamano

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=7vskiw4ooe.fsf@alter.siamese.dyndns.org \
    --to=gitster@pobox.com \
    --cc=casey@nrlssc.navy.mil \
    --cc=git@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.