From lrajchel@ANSI.org  Mon Sep 25 17:48:38 2000
Received: from email1.ansi.org (mail.ansi.org [165.254.114.6])
	by dkuug.dk (8.9.2/8.9.2) with ESMTP id RAA52886;
	Mon, 25 Sep 2000 17:48:38 +0200 (CEST)
	(envelope-from lrajchel@ANSI.org)
Received: by email1.ansi.org with Internet Mail Service (5.5.2650.21)
	id <SMVYT4WB>; Mon, 25 Sep 2000 11:47:47 -0400
Message-ID: <2F81C8110D55D411882A0020356797B2151730@email1.ansi.org>
From: Lisa Rajchel <lrajchel@ANSI.org>
To: "'sc22info@dkuug.dk'" <sc22info@dkuug.dk>
Cc: "'Simonsen, Keld'" <keld.simonsen@dkuug.dk>
Subject: SC 22 N  3180 - Report of the Breakout Session Held During the Se
	ptember 2000 SC 22 Plenary Meeting in Nara, Japan on Extended Character S
	ets in Identifiers
Date: Mon, 25 Sep 2000 11:47:39 -0400
X-Mailer: Internet Mail Service (5.5.2650.21)


_____________________beginning of title page ______________

ISO/IEC JTC 1/SC22
Programming languages, their environments and system software interfaces
Secretariat:  U.S.A.  (ANSI)

ISO/IEC JTC 1/SC22
N3180

TITLE:
Report of the Breakout Session Held During the September 2000 SC 22 Plenary
Meeting in Nara, Japan on Extended Character Sets in Identifiers


DATE ASSIGNED:
2000-09-25

SOURCE:
J. Reid, Chair of the Breakout Session

BACKWARD POINTER:
N/A

DOCUMENT TYPE:
Other (Defined)

PROJECT NUMBER:

STATUS:
This document is circulated for information.

ACTION IDENTIFIER:
FYI to SC22 Member Bodies

DUE DATE:
N/A

DISTRIBUTION:
text

CROSS REFERENCE:

DISTRIBUTION FORM:
Def


Lisa Rajchel
ANSI
11 West 42nd Street
New York, NY  10036
Telephone:  (212) 642-4932
Fax:             (212) 840-2298
Email:  lrajchel@ansi.org <mailto:lrajchel@ansi.org> 

_____________________end of title page _________________________


Breakout session on extended character sets in identifiers
Chair: John Reid
Ms. Bennett sought guidance from WG20 participants and SC22 conveners on
upper/lower-case folding and character equivalence issues related to
extended identifiers in COBOL.  It was determined that the specific issues
identified were not problems because the problematic characters were either
not included in TR 10176 or were handled appropriately in the upper/lower
case mappings in TR 14652.   
This facility is part of the C standard, but is not widely implemented.
There is no requirement that languages provide such a facility.

-----------------------------------------------------------

Breakout session on ISO 15435, the API standard 
Chair: John Reid
WG20 has decided that the API standard should be cast in terms of C. 
It became apparent that no consensus existed among those present on the
utility of providing the API standard at this time. Straw votes were as
follows:
	Cease Continue Undecided/Abstain 
Convenors      1       2       3
Individuals    5       6       4
Countries      5       4       2

