[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: INSTALL nits
From: |
Gavin Smith |
Subject: |
Re: INSTALL nits |
Date: |
Sat, 19 Aug 2023 10:55:12 +0100 |
On Fri, Aug 18, 2023 at 10:02:53PM -0500, Paul Eggert wrote:
> > It would make sense to use "INSTALL.ISO"
> > as INSTALL in packages.
>
> In old-fashioned packages perhaps. Nowadays a lot of packages use UTF-8 in
> their source files anyway.
>
> I understand the reluctance to go beyond ASCII. Long ago I dealt with
> displays that couldn't even handle all of ASCII. But nowadays it generally
> isn't worth worrying about this stuff. Pretty much every builder can deal
> with the UTF-8 characters in INSTALL.
I'm not quite sure whether "builder" here refers to a human being or a
computer.
I was concerned with the case of a person trying to read INSTALL in a
non-UTF-8 terminal. This is possible with e.g. "LC_ALL=C xterm" or in
some MS-Windows terminal windows. People may be on broken or old systems
for whatever reason and may be reading INSTALL on their way to a more
functional system, in order to install software that will fix it. I
agree that it wouldn't matter for a software package that wasn't "system
software" that is installed after everything else on top of a
fully-functioning operating system.
- Re: INSTALL nits, (continued)
- Re: INSTALL nits, Paul Eggert, 2023/08/15
- Re: INSTALL nits, Gavin Smith, 2023/08/17
- Re: INSTALL nits, Bob Friesenhahn, 2023/08/17
- Re: INSTALL nits, Zack Weinberg, 2023/08/17
- Re: INSTALL nits, Peter Johansson, 2023/08/17
- Re: INSTALL nits, Thomas Jahns, 2023/08/18
- Re: INSTALL nits, Paul Eggert, 2023/08/18
- Re: INSTALL nits, Russ Allbery, 2023/08/18
- Re: INSTALL nits, Paul Eggert, 2023/08/18
- Re: INSTALL nits,
Gavin Smith <=
- Re: INSTALL nits, Paul Eggert, 2023/08/20