character encoding ISO 2022

Please forgive my ignorance but what is ISO 2022 exactly?

The choice in the character set negotiation is between:
ISO2022
ISO10646
Private

ISO2022, as I understand it, is an encapsulation of all classic 7-bits and
8-bits character sets.
How many applications use ISO2022?
How do I say I send Ascii, or Latin-1?

Wouldn't it be better, instead of ISO 2022, to make a list (extendable) of
character sets used? We could give them OID's.
I think we need the following:

ASCII
Extended ASCII
ANSI
ALA
Latin-1
Extended-Latin
...

probably a few more


Pieter van Lierop

> -----Message d'origine-----
> De : LeVan,Ralph [mailto:levan@oclc.org]
> Envoyé : mardi 12 mars 2002 20:59
> À : zig
> Objet : RE: back to character encoding
> 
> 
> Yes!  It should apply to the OctetString version of Term.  
> (It does in my
> server.)
> 
> Ralph
> 
> > -----Original Message-----
> > From: Ray Denenberg [mailto:rden@loc.gov]
> > Sent: Tuesday, March 12, 2002 9:56 AM
> > To: zig
> > Subject: Re: back to character encoding
> > 
> > 
> > Pieter Van Lierop wrote:
> > 
> > > I agree. But I would suggest to explicitly include Search 
> > Term when it is
> > > defined as OCTET STRING.
> > 
> > I understand your concern, Pieter, but I don't see any easy 
> > way to accomplish
> > this with the existing character set negotiation definition, 
> > short of amending
> > it (again!). If there is popular support for doing this, 
> > folks need to speak
> > up.
> > 
> > --Ray
> > 
> > 
>

Received on Wednesday, 13 March 2002 05:30:25 UTC