From mboxrd@z Thu Jan 1 00:00:00 1970 X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on polar.synack.me X-Spam-Level: * X-Spam-Status: No, score=1.2 required=5.0 tests=BAYES_00,FROM_WORDY, INVALID_MSGID autolearn=no autolearn_force=no version=3.4.4 X-Google-Language: ENGLISH,ASCII-7-bit X-Google-Thread: 103376,b1a601cc75c5fb67 X-Google-Attributes: gid103376,public From: "Nick Roberts" Subject: Re: String type conversions Date: 1999/02/12 Message-ID: <7a3qmn$e66$3@plug.news.pipex.net>#1/1 X-Deja-AN: 443944610 References: <36C08E00.C3904670@Botton.com> X-MimeOLE: Produced By Microsoft MimeOLE V4.72.3110.3 Organization: UUNET WorldCom server (post doesn't reflect views of UUNET WorldCom) Newsgroups: comp.lang.ada Date: 1999-02-12T00:00:00+00:00 List-Id: Before too long, hopefully, the answer will be "just don't use [8-bit] Character". Most workstations and PCs these days are so powerful - in order to cope with graphics, multimedia, games etc. - that having them handle 16-bit characters (instead of 8-bit/MBCS) most of the time is unlikely to be a problem. And as for long-term file storage: compress. Question: I am currently developing an idea as to a standard graphics/GUI package hierarchy for Ada; would there be any point at all in providing a (nearly duplicate) set of procedures and functions for the 'Character' type, as well as for 'Wide_Character'? ------------------------------------------- Nick Roberts "The Prophylactic Didactic" ------------------------------------------- Robert I. Eachus wrote in message ... [...] | It is a shame that the character mapping arena is such a mess.