[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]


To: ietf-provreg@cafax.se
From: Stephane Bortzmeyer <bortzmeyer@nic.fr>
Date: Tue, 29 Oct 2002 15:16:36 +0100
Content-Disposition: inline
Sender: owner-ietf-provreg@cafax.se
User-Agent: Mutt/1.3.28i
Subject: Internationalized vs. localized

In draft-ietf-provreg-epp-contact-05.txt, one can read:

  - One or two <contact:postalInfo> elements that contain postal address
  information.  Two elements are provided so that address information
  can be provided in both internationalized and localized forms; a
  "type" attribute is used to identify the two forms.  If an
  internationalized form (type="int") is provided, element content MUST
  be represented in a subset of UTF-8 that can be represented in the 7-
  bit US-ASCII character set.  If a localized form (type="loc") is
  provided, element content MAY be represented in unrestricted UTF-8.

The vocabulary is very strange: the international form should be the
encoding allowing full use of Unicode (here, UTF-8). Because it is the
form that works in every country.

A form restricted to US-ASCII should be named "local" because it will
work only in some countries. I suggest to swap "internationalized" and
"localized" in the above text. Or to use less ambiguous words like
"Full repertoire" and "Subset".



Home | Date list | Subject list