From: Jonathan Corbet <corbet@lwn.net>
To: Ben Hutchings <ben@decadent.org.uk>
Cc: "Jérémy Bobbio" <lunar@debian.org>,
reproducible-builds@lists.alioth.debian.org,
linux-doc@vger.kernel.org, "Randy Dunlap" <rdunlap@infradead.org>,
"Michal Marek" <mmarek@suse.com>,
linux-kbuild <linux-kbuild@vger.kernel.org>
Subject: Re: [PATCH 2/2] DocBook: Use a fixed encoding for output
Date: Fri, 11 Sep 2015 13:30:59 -0600 [thread overview]
Message-ID: <20150911133059.77455c16@lwn.net> (raw)
In-Reply-To: <1441147759.9215.44.camel@decadent.org.uk>
On Tue, 01 Sep 2015 23:49:19 +0100
Ben Hutchings <ben@decadent.org.uk> 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
next prev parent reply other threads:[~2015-09-11 19:31 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-01 22:47 [PATCH 0/2] More reproducible document builds Ben Hutchings
2015-09-01 22:49 ` [PATCH 2/2] DocBook: Use a fixed encoding for output Ben Hutchings
2015-09-11 19:30 ` Jonathan Corbet [this message]
2015-09-11 21:40 ` [Reproducible-builds] " Daniel Kahn Gillmor
2015-09-12 20:06 ` Jonathan Corbet
2015-09-14 0:32 ` Ben Hutchings
2015-09-18 16:30 ` Jonathan Corbet
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20150911133059.77455c16@lwn.net \
--to=corbet@lwn.net \
--cc=ben@decadent.org.uk \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kbuild@vger.kernel.org \
--cc=lunar@debian.org \
--cc=mmarek@suse.com \
--cc=rdunlap@infradead.org \
--cc=reproducible-builds@lists.alioth.debian.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox