From owner-freebsd-ports@FreeBSD.ORG Sat Jan 13 19:01:22 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 7DBE316A40F for ; Sat, 13 Jan 2007 19:01:22 +0000 (UTC) (envelope-from infofarmer@gmail.com) Received: from ug-out-1314.google.com (ug-out-1314.google.com [66.249.92.173]) by mx1.freebsd.org (Postfix) with ESMTP id 1CB0313C45A for ; Sat, 13 Jan 2007 19:01:21 +0000 (UTC) (envelope-from infofarmer@gmail.com) Received: by ug-out-1314.google.com with SMTP id o2so941046uge for ; Sat, 13 Jan 2007 11:01:20 -0800 (PST) DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:sender:to:subject:mime-version:content-type:content-transfer-encoding:content-disposition:x-google-sender-auth; b=RQgIux2Jrc7vsXTFosyDfYwuvKOYfPIfQRBlwRp/39xW6OuGcVSQ1aUA2DcJPMei6Cosy1dVEFzy20DD+H2qJEZoOOOcfFDxpK7tRB4vzjjzjG8GD4E8rS/B3vkQHWNzrXSHpGVbx8wpAilZ5EtKJM0khicfeoH2A3bcV8biJJI= Received: by 10.78.166.7 with SMTP id o7mr1324884hue.1168714880456; Sat, 13 Jan 2007 11:01:20 -0800 (PST) Received: by 10.78.164.20 with HTTP; Sat, 13 Jan 2007 11:01:20 -0800 (PST) Message-ID: Date: Sat, 13 Jan 2007 22:01:20 +0300 From: "Andrew Pantyukhin" Sender: infofarmer@gmail.com To: "FreeBSD Ports" MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline X-Google-Sender-Auth: d11c7b20ec5bf18d Cc: Subject: 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: Sat, 13 Jan 2007 19:01:22 -0000 I'm not sure if there's a policy already, but it seems we have discussed this before. Can we limit /usr/ports (the whole ports collection) to English language and ASCII characters? This restriction should probably apply to all text data (with possible exception for patches). I know many of us would like to see i18n/l10n efforts in ports collection, but for now, in my opinion, we might need to focus on plain English. I'll start poking maintainers soon if there's no articulate objection.