ISO/IEC JTC 1/SC 2 N 3155
DATE: 1998-08-05
  
ISO/IEC JTC 1/SC 2 
Coded Character Sets 
Secretariat: Japan (JISC)
 
 
DOC TYPE:   National Body Contribution 
 
TITLE:  
 		 National Body Comments on SC 2 N 3087: Application for Registration No 204, Supplementary set for Latin-1 alternative with EURO SIGN
SOURCE:  
 		 National Bodies of Canada, UK and US
PROJECT:  
 		 --
STATUS:  
 		 These comments are forwarded to the Registration Authority for consideration.
ACTION ID:  
 		 FYI
DUE DATE:    
DISTRIBUTION:   P, O and L Members of ISO/IEC JTC 1/SC 2 
WG Conveners, Secretariats 
ISO/IEC JTC 1 Secretariat 
ISO/IEC ITTF 
 
NO. OF PAGES: 
 		 2
ACCESS LEVEL: 
 		 Open
WEB ISSUE #:  
 		 024
Secretariat ISO/IEC JTC 1/SC 2 - Toshiko KIMURA
IPSJ/ITSCJ (Information Processing Society of Japan/Information Technology Standards Commission of Japan)*
Room 308-3, Kikai-Shinko-Kaikan Bldg., 3-5-8, Shiba-Koen, Minato-ku, Tokyo 105 JAPAN
Tel: +81 3 3431 2808; Fax: +81 3 3431 6493; Email: kimura@itscj.ipsj.or.jp
*A Standard Organization accredited by JISC


Canada

Due date 1998 07 31
Document number  JTC1/SC2N3087 Application for Registration No.204:Supplementary set for Latin-1 alternative with EURO SIGN

Canada agrees with the registration - with the following comment.
This registration seems to be questionable on the basis that Latin-9 is almost an IS.
However, Canada recognises that there are some vendor code sets in support of the EURO SIGN which do match the repertoire being registered along with the G0 of  Latin-1.


UK

The UK approves Registration Nos. 203, 204, 205, 206.


US

The U.S. Vote for Registration # 204  Latin-1 supplement

Document: SC2 N 3087

The U.S. vote is to disapprove.

Comments:
 It is not necessary since 8859-15 has been approved.  This will be too costly for vendors to implement and we see little commercial value in this registration.

These registration is simply an invitations to more 2022 mischief and interoperability problems with data that is *almost* like Latin-1, Latin-4, or Latin-7, except for a single character. In our view, this is a recapitulation of the ISO 646 national variant currency nonsense and should be completely eschewed in favor of full 10646 implementations to get  EURO SIGN support.