From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from tex.lwn.net ([70.33.254.29]:59353 "EHLO vena.lwn.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751426AbbIKTbA (ORCPT ); Fri, 11 Sep 2015 15:31:00 -0400 Date: Fri, 11 Sep 2015 13:30:59 -0600 From: Jonathan Corbet Subject: Re: [PATCH 2/2] DocBook: Use a fixed encoding for output Message-ID: <20150911133059.77455c16@lwn.net> In-Reply-To: <1441147759.9215.44.camel@decadent.org.uk> References: <1441147632.9215.42.camel@decadent.org.uk> <1441147759.9215.44.camel@decadent.org.uk> MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 8bit Sender: linux-kbuild-owner@vger.kernel.org List-ID: To: Ben Hutchings Cc: =?UTF-8?B?SsOpcsOpbXk=?= Bobbio , reproducible-builds@lists.alioth.debian.org, linux-doc@vger.kernel.org, Randy Dunlap , Michal Marek , linux-kbuild On Tue, 01 Sep 2015 23:49:19 +0100 Ben Hutchings wrote: > Currently the encoding of documents generated by DocBook depends on > the current locale. Make the output reproducible independently of > the locale, by setting the encoding to UTF-8 (LC_CTYPE=C.UTF-8) by > preference, or ASCII (LC_CTYPE=C) as a fallback. I guess I have to ask, though: doesn't it seem that having the docs produced according to the current locale is the Right Thing to do? Users have their locale set as it is for a reason, it seems like the production of textual documents should respect their choice. Am I missing something here? Thanks, jon