Xref: utzoo comp.emacs:4558 comp.lang.c:13779 comp.sys.ibm.pc:20819
Path: utzoo!attcan!uunet!lll-winken!lll-tis!helios.ee.lbl.gov!pasteur!ames!haven!adm!smoke!gwyn
From: gwyn@smoke.BRL.MIL (Doug Gwyn )
Newsgroups: comp.emacs,comp.lang.c,comp.sys.ibm.pc
Subject: Re: Programming and international character sets.
Message-ID: <8817@smoke.BRL.MIL>
Date: 2 Nov 88 17:25:20 GMT
References: <532@krafla.rhi.hi.is> <8804@smoke.BRL.MIL> <207@jhereg.Jhereg.MN.ORG>
Reply-To: gwyn@brl.arpa (Doug Gwyn (VLD/VMB) <gwyn>)
Organization: Ballistic Research Lab (BRL), APG, MD.
Lines: 14

In article <207@jhereg.Jhereg.MN.ORG> mark@jhereg.MN.ORG (Mark H. Colburn) writes:
>Unfortunately, the C standard is still lacking in this area.  It is true
>that the attempt was made, however, X3J11 will have to go through another
>round if it is to be truly internationalized.

Not really; all the issues you raised in your posting were already addressed
in arriving at the current draft proposed C Standard, which had the assistance
and approval of several specialists in internationalization.  I don't want to
try to discuss the details here; however, I will remark that the wchar_t type
is NOT intended to be used in all the contexts where a character would
normally be used in an 8-bit environment.  ITSCJ indicated that the functions
provided were sufficient.  Others can of course be provided as extensions but
were not felt to be sufficiently important to standardize.

P.S. This is not to be taken as an official X3J11 statement!