home *** CD-ROM | disk | FTP | other *** search
/ NetNews Usenet Archive 1992 #18 / NN_1992_18.iso / spool / comp / std / internat / 619 < prev    next >
Encoding:
Text File  |  1992-08-14  |  1.2 KB  |  32 lines
  1. Newsgroups: comp.std.internat
  2. Path: sparky!uunet!haven.umd.edu!darwin.sura.net!wupost!cs.utexas.edu!sun-barr!ames!data.nas.nasa.gov!taligent!tseng
  3. From: jenkinsj@blowfish.taligent.com (John H. Jenkins)
  4. Subject: Re: ISO 10646 the final character set?
  5. Message-ID: <jenkinsj-140892082346@tseng.taligent.com>
  6. Followup-To: comp.std.internat,comp.misc
  7. Sender: usenet@taligent.com (More Bytes Than You Can Read)
  8. Organization: Taligent, Inc.
  9. References: <Bswu4x.80r@immd4.informatik.uni-erlangen.de> <23303A@erik.naggum.no> <jenkinsj-130892151628@tseng.taligent.com><1992Aug14.051609.8673@jyu.fi>
  10. Date: Fri, 14 Aug 1992 15:28:06 GMT
  11. Lines: 19
  12.  
  13. In article <1992Aug14.051609.8673@jyu.fi>, sakkinen@jyu.fi (Markku
  14. Sakkinen) wrote:
  15. > 
  16. > I don't think that the stupid idiosyncrasies of one particular
  17. > programming language should be taken into account when a long-time
  18. > universal character code is defined.
  19. > 
  20.  
  21. Hearty agreement here.  The problem came from the fact that a lot of
  22. organizations with a lot of clout were fighting 10646 tooth and nail
  23. because of its perceived incompatibility with C.  The name-change
  24. proposal is an indication of how desperate people were getting in trying
  25. to combat this misperception. 
  26.  
  27.  
  28. ----
  29. John H. Jenkins
  30. John_Jenkins@taligent.com
  31.  
  32.