[I18n-sig] naming codecs

M.-A. Lemburg mal@lemburg.com
Wed, 06 Dec 2000 12:26:52 +0100

Tamito KAJIYAMA wrote:
> Hi all,
> I'd like to receive some suggestions about the naming of a codec.
> 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.
> I believe there is a demand for the codec, but I have no idea
> on the name of the codec.  I'd like to give it a name that is
> different from all standard encoding names, since the encoding
> for which the codec works is not defined as a standard
> (e.g. RFCs).  I'd also like to avoid an encoding name that is
> likely to be used as a standard encoding name in the future.
> Does anyone have a good name for the codec?  Or, how may I think
> about the naming of a codec?  Any suggestions are welcome.

Why not simply append another "-<variant>" part to the name,
e.g. "iso-2022-jp-hw" or "iso-2022-jp-extended" ?

Marc-Andre Lemburg
Company:                                        http://www.egenix.com/
Consulting:                                    http://www.lemburg.com/
Python Pages:                           http://www.lemburg.com/python/