From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 10570 invoked from network); 19 Dec 2002 16:32:54 -0000 Received: from sunsite.dk (130.225.247.90) by ns1.primenet.com.au with SMTP; 19 Dec 2002 16:32:54 -0000 Received: (qmail 24037 invoked by alias); 19 Dec 2002 16:32:34 -0000 Mailing-List: contact zsh-workers-help@sunsite.dk; run by ezmlm Precedence: bulk X-No-Archive: yes X-Seq: 18020 Received: (qmail 23986 invoked from network); 19 Dec 2002 16:32:28 -0000 Date: Thu, 19 Dec 2002 17:34:35 +0100 From: DervishD To: Zsh Subject: What can we do with the drunken libc? Message-ID: <20021219163435.GA2285@DervishD> Mail-Followup-To: Zsh Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit User-Agent: Mutt/1.4i Organization: Pleyades User-Agent: Mutt/1.4i Hi all :)) Excuse the subject, it's just that I'm starting to be pissed off by GNUisms... Let's go to the matter. In the GNU libc 'ldd' script, we can see something like: echo $"Usage: ldd [OPTION]... FILE..." Obviously, zsh prints '$Usage: ....', but bash prints just 'Usage: ...'. Why? Well, because as the bash documentation says, a doubled quoted string preceeded by a dollar sign, will cause the string to be translated according to the current locale. There are a couple of shell variables involved, too, TEXTDOMAIN and TEXTDOMAINDIR. Well. What can we, zsh users, do? First thing is to use bash as our '/bin/sh' so all that crappy GNUist scripts work as expected (there are more bashisms). Other thing is making zsh support those bashist features. And the most difficult, trying to convince the GNU people to write portable shell scripts that work with any POSIX or SUSv3 compatible shell... In the interim, GNU people gives me the freedom to use bash, bash or even bash as my /bin/sh if I run GNU libc. That's freedom. Just my 0.02 EUR Raśl