From owner-freebsd-ports  Sun Mar  2 09:09:15 1997
Return-Path: <owner-ports>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.5/8.8.5) id JAA21477
          for ports-outgoing; Sun, 2 Mar 1997 09:09:15 -0800 (PST)
Received: from fallout.campusview.indiana.edu (fallout.campusview.indiana.edu [149.159.1.1])
          by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id JAA21470
          for <ports@freebsd.org>; Sun, 2 Mar 1997 09:09:13 -0800 (PST)
Received: from localhost (jfieber@localhost)
	by fallout.campusview.indiana.edu (8.8.5/8.8.5) with SMTP id MAA20021;
	Sun, 2 Mar 1997 12:09:02 -0500 (EST)
Date: Sun, 2 Mar 1997 12:09:02 -0500 (EST)
From: John Fieber <jfieber@indiana.edu>
To: Satoshi Asami <asami@vader.cs.berkeley.edu>
cc: ports@freebsd.org
Subject: Re: new category for multilingual ports?
In-Reply-To: <199703021411.GAA10436@baloon.mimi.com>
Message-ID: <Pine.BSF.3.95q.970302115603.18125D-100000@fallout.campusview.indiana.edu>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-ports@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

On Sun, 2 Mar 1997, Satoshi Asami wrote:

> There are a couple of ports in incoming from Japanese people that are
> actually generic multilingual ports.  What about a new category for
> these?  Some ideas:
> 
> international
> multilingual
> i18n (I hate this word, but this seems like the common abb8n)

It strikes me a slightly odd that properly internationalized
software should needs its own category.  After all, should all
software be properly internationalized?   (okay, I'm dreaming a
bit...)

How about an "arrogant-us-english-only-imperial-software" ports
category to put things in proper perspective?

-john