public inbox for linux-kbuild@vger.kernel.org
 help / color / mirror / Atom feed
From: Jonathan Corbet <corbet@lwn.net>
To: Daniel Kahn Gillmor <dkg@fifthhorseman.net>
Cc: "Ben Hutchings" <ben@decadent.org.uk>,
	"Randy Dunlap" <rdunlap@infradead.org>,
	linux-kbuild <linux-kbuild@vger.kernel.org>,
	"Jérémy Bobbio" <lunar@debian.org>,
	linux-doc@vger.kernel.org, "Michal Marek" <mmarek@suse.com>,
	reproducible-builds@lists.alioth.debian.org
Subject: Re: [Reproducible-builds] [PATCH 2/2] DocBook: Use a fixed encoding for output
Date: Sat, 12 Sep 2015 14:06:16 -0600	[thread overview]
Message-ID: <20150912140616.672b5d5a@lwn.net> (raw)
In-Reply-To: <878u8ceisu.fsf@alice.fifthhorseman.net>

On Fri, 11 Sep 2015 17:40:33 -0400
Daniel Kahn Gillmor <dkg@fifthhorseman.net> wrote:

> I sympathize with Jonathan's general concern here -- if this patchset
> makes it impossible for people to build documentation with (for example)
> their preferred collation order, it would be suboptimal.
> 
> On the other hand, this seems to focus on character encodings
> specifically; do we really want to encourage any sort of encodings other
> than UTF-8?  The only plausible arguments i've heard for documents that
> are exclusively CJK characters, which could achieve a modest size
> reduction using more targeted encodings.  afaik, there are no such
> documents in the kernel, and i doubt there ever will be.

Well, there are CJK documents in the kernel, actually, though none are in
the DocBook directory currently.

Regardless of this, it's not a matter of which encodings we are
encouraging.  If we want to encourage utf-8 use, we might not want to
start in the kernel's documentation directory.  I think we need to
respect the user's choice in this regard and not try to override it.  If
I take this patch, I suspect somebody will yell at me for it...

With regard to reproducible builds: success in this area certainly
requires reproducing the build environment as well.  Honestly, I think
that needs to include the locale settings.

Let me know if you think I've totally misunderstood things.

jon

  reply	other threads:[~2015-09-12 20:06 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
2015-09-11 21:40     ` [Reproducible-builds] " Daniel Kahn Gillmor
2015-09-12 20:06       ` Jonathan Corbet [this message]
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=20150912140616.672b5d5a@lwn.net \
    --to=corbet@lwn.net \
    --cc=ben@decadent.org.uk \
    --cc=dkg@fifthhorseman.net \
    --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