Re: Spurious warning generated by bash

On 2026-01-01 03:41, matthew patton wrote:
> since when is it acceptable to have UTF-8 format files as shell scripts, perl scripts or even python programs?

1992 X/Open USL Dave Prosser, Plan 9 Ken Thompson, Rob Pike; 1993 USENIX, 
Unicode, ISO/IEC 10646; IETF 1998.

> a directive in .vimrc can probably help. along the lines of
> 
> au BefRead,ButNewFile *.sh,*.pl,*.py set nobomb
> or if you invoke your shell script with `bash --utf8 ./my_broken^H^H^H^Hutf-encoded.script`
> or just `LANG=C.UTF-8 ./my_utf8-script` or set LC_ALL etc.
Never had any problems since switching when Windows supported chcp 65001, and 
Cygwin and libraries got decent support for UTF-8 translations for apps, and 
UTF-8 Compose support, maybe about 5-10 years ago.

> you know how people pose the question "if you could go back in time, would you kill Hitler? 

You say that as if anyone would not try.

 > Same needs to be asked about the person/committee that came up with UTF8.

No one should make such a comment about character sets and developers, or most 
other tech topics.

	https://en.wikipedia.org/wiki/UTF-8:

"...fewer internationalization issues than any alternative text encoding.

UTF-8 is dominant for all countries/languages on the internet, is used in most 
standards, often the only allowed encoding, and is supported by all modern 
operating systems and programming languages."

Happy New Year! ;^>

-- 
Take care. Thanks, Brian Inglis              Calgary, Alberta, Canada

La perfection est atteinte                   Perfection is achieved
non pas lorsqu'il n'y a plus rien à ajouter  not when there is no more to add
mais lorsqu'il n'y a plus rien à retrancher  but when there is no more to cut
                                 -- Antoine de Saint-Exupéry

-- 
Problem reports:      https://cygwin.com/problems.html
FAQ:                  https://cygwin.com/faq/
Documentation:        https://cygwin.com/docs.html
Unsubscribe info:     https://cygwin.com/ml/#unsubscribe-simple