Date: Mon, 16 Nov 2015 18:35:03 +0100 From: Ed Schouten <ed@nuxi.nl> To: Baptiste Daroussin <bapt@freebsd.org> Cc: arch@freebsd.org, marino@freebsd.org Subject: Re: Question about ASCII and nl_langinfo (locale work) Message-ID: <CABh_MKkAJmfTrT5qMwvcOcFAviD9h8okOnsH7PJ2x7gxFvY5Yw@mail.gmail.com> In-Reply-To: <20151110222636.GN10134@ivaldir.etoilebsd.net> References: <20151110222636.GN10134@ivaldir.etoilebsd.net>
next in thread | previous in thread | raw e-mail | index | archive | help
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 <ed@nuxi.nl> Nuxi, 's-Hertogenbosch, the Netherlands KvK-nr.: 62051717
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CABh_MKkAJmfTrT5qMwvcOcFAviD9h8okOnsH7PJ2x7gxFvY5Yw>