public inbox for libc-alpha@sourceware.org
 help / color / mirror / Atom feed
From: Florian Weimer <fweimer@redhat.com>
To: Mark Wielaard <mark@klomp.org>
Cc: libc-alpha@sourceware.org,
	 "Andreas K . Huettel" <dilfridge@gentoo.org>,
	 Siddhesh Poyarekar <siddhesh@gotplt.org>,
	 Paul Eggert <eggert@cs.ucla.edu>
Subject: Re: [PATCH] Make sure INSTALL is ASCII plaintext again
Date: Mon, 29 Apr 2024 14:53:06 +0200	[thread overview]
Message-ID: <87v840uy8d.fsf@oldenburg.str.redhat.com> (raw)
In-Reply-To: <20240428145939.1526515-1-mark@klomp.org> (Mark Wielaard's message of "Sun, 28 Apr 2024 16:59:39 +0200")

* Mark Wielaard:

> This reverts commit 84e93afc7 ("Switch to UTF-8 for INSTALL") and
> reinstates commit c14f2e4aa ("Make sure INSTALL is ASCII plaintext")
> and regenerates INSTALL.
>
> It turns out that different versions of makeinfo (texinfo/texi2any),
> at least versions 7.0.3 and 7.1, put unicode quote glyphs in different
> places (specifically whether contractions like you'd, don't, aren't or
> you'll use ’ or '). This breaks the make dist target as used for
> (snapshot) releases, which have a check on the regenerated INSTALL
> file. Using --disable-encoding generates the same plaintext ASCII on
> all versions.
>
> An alternative would be to regenerate INSTALL with texinfo 7.1 and
> require that at least that version. But that seems too soon while
> various distros don't have 7.1 yet. We can try again to use UTF-8 for
> INSTALL in a couple of years.

Looks reasonable, thanks.

Reviewed-by: Florian Weimer <fweimer@redhat.com>

Florian


  reply	other threads:[~2024-04-29 12:53 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-04-28 14:59 Mark Wielaard
2024-04-29 12:53 ` Florian Weimer [this message]
2024-04-30  9:36   ` Mark Wielaard

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=87v840uy8d.fsf@oldenburg.str.redhat.com \
    --to=fweimer@redhat.com \
    --cc=dilfridge@gentoo.org \
    --cc=eggert@cs.ucla.edu \
    --cc=libc-alpha@sourceware.org \
    --cc=mark@klomp.org \
    --cc=siddhesh@gotplt.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).