From ... Path: archiver1.google.com!news1.google.com!newsfeed.stanford.edu!news-spur1.maxwell.syr.edu!news.maxwell.syr.edu!tank.news.pipex.net!pipex!newsfeed.esat.net!nslave.kpnqwest.net!nloc.kpnqwest.net!nmaster.kpnqwest.net!nreader2.kpnqwest.net.POSTED!not-for-mail Newsgroups: comp.lang.lisp Subject: Re: Beginner question: performance problems with a simple program References: <36sW7.19$Mv6.41773@burlma1-snr2> <3218911701617481@naggum.net> Mail-Copies-To: never From: Erik Naggum Message-ID: <3218921950422847@naggum.net> Organization: Naggum Software, Oslo, Norway Lines: 31 User-Agent: Gnus/5.09 (Gnus v5.9.0) Emacs/21.1 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 02 Jan 2002 00:59:11 GMT X-Complaints-To: newsmaster@KPNQwest.no X-Trace: nreader2.kpnqwest.net 1009933151 193.71.66.49 (Wed, 02 Jan 2002 01:59:11 MET) NNTP-Posting-Date: Wed, 02 Jan 2002 01:59:11 MET Xref: archiver1.google.com comp.lang.lisp:23450 * Thomas F. Burdick | Certainly the idea of locales can be (and is) taken to a silly extreme. | However, there are a few languages that are really important, and being | able to deliver applications in them is important. English, Spanish, | maybe French, Arabic, Chinese, and Japanese, should all be usable. We | should be able to assume that all programmers have at least basic English | skills, but the same is not true of users. Well, you cannot write a program that works in English, Spanish, French, Arabic, Chinese and Japanese unless you know _all_ these languages and _prepare_ for the translation. The only way to make a program work in more than one language is to make it work in _none_: formalize a protocol and write user-interface front- ends to it. Let those who understand the application _and_ the target language write that user-interface front-end. English happens to be the _common_ language of the field of computer science. It no longer has the role of a natural language in computer science. That this leaves a large number of people "handicapped" by being misled to believe that _their_ language is the common language, is nothing but unfortunate. Forget the whole locale business and write software that speaks about objects and units and internal stuff, and let several user-interface guys handle the user-interface portion that talks to people in various cultures. This is not hard at all, once you get past the misguided notion that all computer programs should talk directly to users. /// --