- From: Keld Jørn Simonsen <keld@dkuug.dk>
- Date: Mon, 29 Jul 2002 17:39:54 +0200
- To: Mark Davis <mark.davis@us.ibm.com>
- Cc: Markus Scherer <markus.scherer@jtcsv.com>, charsets <ietf-charsets@iana.org>
On Mon, Jul 22, 2002 at 06:36:26PM -0700, Mark Davis wrote:
>
>
>
>
>
>
> 2. The character set that is actually in use are A-Z, 0-9 plus:
>
> '_', example: ANSI_X3.110-1983
> '.', example: ANSI_X3.110-1983
> '-', example: ANSI_X3.110-1983
> ':', example: ISO_5427:1981
> '+', example: PC-MULTILINGUAL-850+EURO
> '(', example: NF_Z_62-010_(1973)
> ')', example: NF_Z_62-010_(1973)
>
> Notice that the last two are in violation of http://www.ietf.
> org/rfc/rfc2978.txt, and should be removed!
Or, the RFC2978 should be changed to accomodate these.
the registrations came before the RFC2978, and the RFC tries to
accomodate all the registrations. Furthermore it is against all
recommendations on registries to remove items from them.
>
> A. Replace the text:
>
> The character set names may be up to 40 characters taken from the
> printable characters of US-ASCII. However, no distinction is made
> between use of upper and lower case letters.
>
> with the new text:
>
> Constraints on Registered Names and Aliases
>
> The character set names may be up to 45 characters taken from the printable
> characters of US-ASCII. As per RFC 2978 no distinction is made between use
> of upper and lower case letters. While more punctuation characters are
> permitted by RFC 2978, only the following should be used:
> 0x43 '+' PLUS SIGN
> 0x45 '-' HYPHEN-MINUS
> 0x46 '.' FULL STOP
> 0x58 ':' COLON
> 0x95 '_' LOW LINE
and then also add
0x28 '(' LEFT PARENTHESIS
0x29 ')' RIGHT PARENTHESIS
Kind regards
Keld
Received on Monday, 29 July 2002 11:39:11 UTC