[I18n-sig] naming codecs

Martin v. Loewis martin@loewis.home.cs.tu-berlin.de
Wed, 6 Dec 2000 20:13:22 +0100

> I consider releasing a version of the JapaneseCodecs package
> that will include a new codec for a variant of ISO-2022-JP.  The
> codec is almost the same as the ISO-2022-JP codec, but it can
> encode and decode Halfwidth Katakana (U+FF61 to U+FF9F) which
> can not be encoded with ISO-2022-JP as defined in RFC1468.

So how exactly does it encode them? 

Is that your own invention, or is there some precedent for that
encoding (e.g. in an operating system, or text processing system)?

> I believe there is a demand for the codec, but I have no idea on the
> name of the codec.

If it is your own invention, I'd be surprised if there was demand. If
you just follow some existing practice, then I'd assume that this
practice has a name - which should be used in the name of the codec.