From asmusf@ix.netcom.com  Tue Sep 30 02:43:50 1997
Received: from dfw-ix12.ix.netcom.com (dfw-ix12.ix.netcom.com [206.214.98.12]) by dkuug.dk (8.6.12/8.6.12) with ESMTP id CAA15605; Tue, 30 Sep 1997 02:43:47 +0100
Received: (from smap@localhost)
          by dfw-ix12.ix.netcom.com (8.8.4/8.8.4)
	  id UAA25002; Mon, 29 Sep 1997 20:43:09 -0500 (CDT)
Received: from tide12.microsoft.com(131.107.3.22) by dfw-ix12.ix.netcom.com via smap (V1.3)
	id rma024931; Mon Sep 29 20:42:26 1997
Message-Id: <1.5.4.32.19970930014155.00a97de8@popd.ix.netcom.com>
X-Sender: asmusf@popd.ix.netcom.com
X-Mailer: Windows Eudora Light Version 1.5.4 (32)
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Date: Mon, 29 Sep 1997 18:41:55 -0700
To: keld@dkuug.dk (Keld J|rn Simonsen)
From: Asmus Freytag <asmusf@ix.netcom.com>
Subject: Re: (i18n.373) euro
Cc: i18n@dkuug.dk

At 08:28 PM 09/27/97 +0200, you wrote:
>I got a number of replies telling me that the conversion rate
>between the euro and each individual national currency in the EMU
>is going to be fixed for the duration of the transition period.
>The rate is thus a good candidate for an entry in a locale.

This is bad engineering. Not all information about a country or its currency
belongs in a "locale". In fact, this is a perfect example of what is broken in
the standard POSIX approach to locales. The correct way would involve using
a locale to access that information from an object that knows about currencies.
Look no further than the Java JDK 1.1 for an example of how to structure
things differently and with more expressive power and extensibility.

A./