Edits - Issues 32, 33, and 129
                        SELECTED_CHAR_KIND

Introduction
  Issues 32, 33, and 129, (pp.  40, 349), ask whether the definition of SELECTED_CHAR_KIND requires a
processor to support the ASCII character kind.  They also raise related questions about the wording of the
normative text for SELECTED_CHAR_KIND.

  In a plenary discussion, J3 reaffirmed that processors should not be required to support the ASCII character
kind.

Edits
  The following edits refer to 99-007r2.
7:6       Add the following reference:
ISO / IEC 10646-1:1993, Information Technology - Universal Multiple-Octet Coded Character Set (UCS) - Part 1: 
  Architecture and Basic Multilingual Plane.

40:4-13     Delete the J3 internal note.

349:7-11  Replace the first two sentences of the "Result Value" paragraph with the following:
If NAME has the value DEFAULT, then the result has a value equal to the value of the kind type parameter of the
default character data type.  If NAME has the value ASCII, then the result has a value equal to the value of the
kind type parameter of the ASCII character data type if the processor supports such a type; otherwise the result
has the value -1.  If NAME has the value ISO_10646, then the result has the value of the kind type parameter of
the ISO / IEC 10646-1:1993 UCS-4 character data type if the processor supports such a type; otherwise the result
has the value -1.

349:17-19 Replace the J3 internal note with a regular note.
NOTE 13.15a
ISO_10646 refers to the UCS-4 representation, a 4 octet character set.

349:20-25 Delete the J3 internal note.

References
J3 / 99-222r2, "Responses to WG5/N1356"
J3 / 99-232, "Revisit SELECTED_CHAR_KIND"
J3 / 99-251, "Issues 33 and 129 (ASCII and ISO 10646)"

[End of J3 / 99-259]