From owner-freebsd-ports@FreeBSD.ORG Sun Jan 14 06:28:45 2007 Return-Path: X-Original-To: ports@freebsd.org Delivered-To: freebsd-ports@FreeBSD.ORG Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 2029016A5CB for ; Sun, 14 Jan 2007 06:28:45 +0000 (UTC) (envelope-from dougb@FreeBSD.org) Received: from mail2.fluidhosting.com (mx22.fluidhosting.com [204.14.89.5]) by mx1.freebsd.org (Postfix) with SMTP id 78CCE13C7AD for ; Sun, 14 Jan 2007 06:28:44 +0000 (UTC) (envelope-from dougb@FreeBSD.org) Received: (qmail 2244 invoked by uid 399); 14 Jan 2007 06:28:43 -0000 Received: from localhost (HELO ?192.168.0.5?) (dougb@dougbarton.us@127.0.0.1) by localhost with SMTP; 14 Jan 2007 06:28:43 -0000 X-Originating-IP: 127.0.0.1 Message-ID: <45A9CD99.8040601@FreeBSD.org> Date: Sat, 13 Jan 2007 22:28:41 -0800 From: Doug Barton Organization: http://www.FreeBSD.org/ User-Agent: Thunderbird 1.5.0.9 (Windows/20061207) MIME-Version: 1.0 To: Andrew Pantyukhin References: <17833.15710.478810.6251@jerusalem.litteratus.org> <45A96382.3040407@FreeBSD.org> In-Reply-To: X-Enigmail-Version: 0.94.1.1 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: FreeBSD Ports Subject: Re: Restricting (human) language and character set in /usr/ports X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 14 Jan 2007 06:28:45 -0000 Andrew Pantyukhin wrote: > On 1/14/07, Doug Barton wrote: >> Andrew Pantyukhin wrote: >> > It depends on what you mean by /status quo/, but in >> > short, when I look at COMMENT, pkg-descr, pkg-message, >> > comments in Makefile and other such text data, I >> > expect to see English language and ASCII characters. >> > >> > There are ports that don't follow this expectation and >> > I'd like to change that. >> >> I'm not sure it's quite so cut and dry as that. For example, I think >> it's probably reasonable for the /usr/ports/ ports to have >> some non-ascii stuff to start with. > > I'm not against non-ascii, but there's no notion > of character set in /usr/ports. Now that is a whole different kettle of fish. :) > I work in UTF-8 > and it's visible to me, as it is to many other > people working in many different charsets. Right, and the problem is only going to get worse as more people from other countries and backgrounds get involved. > There are several ways to deal with non-ascii > characters, the two most effective being: > (a) select a universal charset (I would love to > see UTF-8 in that role) I think that's a conversation worth having. > (b) introduce special markers, defining current > charset > > I can not agree with people selecting random > charsets and me having to guess them. Automated > information brokers, like freshports, also have > problems with this. If you're going to open the can of worms involving the bigger picture, then I'd rather refrain from picking nits in this context. If what you're actually suggesting is, "Until we resolve this issue more thoroughly, it would be nice if we were ascii-only in the official parts of a port," you get no objection from me. I think for now it might be reasonable to be more flexible with comments, but I won't quibble. > As for the language, I expect everything within > the FreeBSD project to be present at least in > English. I think this is reasonable as a "lowest common denominator" type of accommodation. Doug -- This .signature sanitized for your protection