From owner-freebsd-arch@freebsd.org Mon Nov 16 17:35:04 2015 Return-Path: Delivered-To: freebsd-arch@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 948D9A303C5 for ; Mon, 16 Nov 2015 17:35:04 +0000 (UTC) (envelope-from ed@nuxi.nl) Received: from mailman.ysv.freebsd.org (mailman.ysv.freebsd.org [IPv6:2001:1900:2254:206a::50:5]) by mx1.freebsd.org (Postfix) with ESMTP id 70E93175E for ; Mon, 16 Nov 2015 17:35:04 +0000 (UTC) (envelope-from ed@nuxi.nl) Received: by mailman.ysv.freebsd.org (Postfix) id 6CE63A303C4; Mon, 16 Nov 2015 17:35:04 +0000 (UTC) Delivered-To: arch@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 6C7D3A303C3 for ; Mon, 16 Nov 2015 17:35:04 +0000 (UTC) (envelope-from ed@nuxi.nl) Received: from mail-yk0-x231.google.com (mail-yk0-x231.google.com [IPv6:2607:f8b0:4002:c07::231]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 28660175A for ; Mon, 16 Nov 2015 17:35:04 +0000 (UTC) (envelope-from ed@nuxi.nl) Received: by ykdr82 with SMTP id r82so251044346ykd.3 for ; Mon, 16 Nov 2015 09:35:03 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=nuxi_nl.20150623.gappssmtp.com; s=20150623; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=w+SQfdug50iXZwXDn5BlfBJyw4MaUv9ukVYfol3CLKA=; b=BETBEBMvh6u5MukF6nn54Xmk4TWVlfYd5AUTLAvzKSVa4ZjGa+0Vn0kBRlKIn3shQd 7mffu83ul33O8bQaOwT0BoUmkOtVKzHPOUhxmK6pG9XyZxjRVXWay2dKlpC5Mz3xV83Q c0Q8D1aC+Q41uoSrQOtNHH2RIUr+RT2qCC4pfruNgmLGi3sRS3LbM1N4dqVV3GzpCq/j g122ROVIUKqQq4SdSJpNPf/mgKrS3Zy7KH0SbzA9/YNTDZVkQiLz+kl3qET4h3QRi7Er UI986CppEw8lJGjABW5QVMLnbVyrklJ322aEWIrnV+vndqWu8dUoMDo7uZXtMfJWGtUi cgyA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type; bh=w+SQfdug50iXZwXDn5BlfBJyw4MaUv9ukVYfol3CLKA=; b=bIzocc8Aw7TQDiDXpWJ9UqNfJiS/i77dp7FWmaxMcvxWJ9vaxwbRvkRlsfgQBS2MnK vP7K+NZYS/hEyrG87Zpu6EpAMgnaoy4QcrgSKk0hhX2KUYa2xEXS6cbaZtbLfiaJa82A 4TNhwI8D4afK4A1iKMeNujwqfaY+IhCioFxZ983jO2EcoUIgIoRzOuQ/8rhaXIxnIt7R xt+f60FSOgzVaJVqSJRiCf7d3q7V2IIIWbTfFTQd6LnJTVS0Cm15iM8R/njmmYHDS3xL nhz1aGHa0kDMPoVDC+soaNtOHy+QG9gsAhu1bWVRtNkE3Y6aTlQJ3/iyFkvFaVjKjlj1 pm2g== X-Gm-Message-State: ALoCoQkgAvhK1WwjpvuL4csC90auJkaAEwPkJpdWo/4H/chdgxWM8R04HeCuhe4RT467xFTmbmoR MIME-Version: 1.0 X-Received: by 10.129.96.84 with SMTP id u81mr9581163ywb.80.1447695303136; Mon, 16 Nov 2015 09:35:03 -0800 (PST) Received: by 10.129.105.86 with HTTP; Mon, 16 Nov 2015 09:35:03 -0800 (PST) In-Reply-To: <20151110222636.GN10134@ivaldir.etoilebsd.net> References: <20151110222636.GN10134@ivaldir.etoilebsd.net> Date: Mon, 16 Nov 2015 18:35:03 +0100 Message-ID: Subject: Re: Question about ASCII and nl_langinfo (locale work) From: Ed Schouten To: Baptiste Daroussin Cc: arch@freebsd.org, marino@freebsd.org Content-Type: text/plain; charset=UTF-8 X-BeenThere: freebsd-arch@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Discussion related to FreeBSD architecture List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 16 Nov 2015 17:35:04 -0000 Hi Baptiste, I personally think it's a shame if we were to deviate from returning "US-ASCII", for the reason that "US-ASCII" also happens to be the preferred MIME name for the character set: http://www.iana.org/assignments/character-sets/character-sets.xhtml "ASCII" doesn't even seem to be an alias for this character set. Though "ANSI_X3.4-1968" is an alias for ASCII, I wouldn't even know that this is ASCII without doing a Google search. In my opinion a decent implementation of newlocale() should support any of the character set names and aliases provided on the IANA page, but let nl_langinfo(CODESET) return the preferred MIME name. > That means we need to teach all upstream about US-ASCII all the time. Could you come up with a concrete list of pieces of software that need to be changed? Is it just those three pieces of software that you mentioned above? If so, then I think it would be a shame to make the concession. -- Ed Schouten Nuxi, 's-Hertogenbosch, the Netherlands KvK-nr.: 62051717