Path: ...!eternal-september.org!feeder3.eternal-september.org!news.eternal-september.org!eternal-september.org!.POSTED!not-for-mail
From: saito <saitology9@gmail.com>
Newsgroups: comp.lang.tcl
Subject: Re: Tcl9: source files are interpreted as utf-8 by default
Date: Wed, 8 Jan 2025 17:36:28 -0500
Organization: A noiseless patient Spider
Lines: 24
Message-ID: <vlmulc$3025m$1@dont-email.me>
References: <vjhiar$3f9go$1@dont-email.me> <vljmj2$29vdo$1@dont-email.me>
 <20250107160810.07ddbbe6@lud1.home> <vlllha$2nvqo$2@dont-email.me>
 <20250108113519.42eb3746@lud1.home> <20250108114254.7f56f049@lud1.home>
 <vlm45q$2qvor$2@dont-email.me> <20250108124055.15c92a05@lud1.home>
 <vlmb6q$2sblj$1@dont-email.me> <20250108162339.7c04023e@lud1.home>
 <vlmjs8$2tu2l$1@dont-email.me>
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
Injection-Date: Wed, 08 Jan 2025 23:36:29 +0100 (CET)
Injection-Info: dont-email.me; posting-host="4780325df47bf7be2593fcde0ad9658e";
	logging-data="3147958"; mail-complaints-to="abuse@eternal-september.org";	posting-account="U2FsdGVkX19rqiquwe5XNwprbOcBPMQB"
User-Agent: Mozilla Thunderbird
Cancel-Lock: sha1:H5rVGbFCVgMCx4rgs7JeBpkTxVQ=
Content-Language: en-US
In-Reply-To: <vlmjs8$2tu2l$1@dont-email.me>
Bytes: 2438

On 1/8/2025 2:32 PM, Rich wrote:
> 
>> I did something like that some 15 years ago. But my case involved a
>> migration. I had a ton of legacy iso-8859 files on a system-wide
>> utf-8 Linux system. That caused me problems too, but iconv fixed it.
> 
> In my case, I used the \uxxxx escapes for anything that was not plain
> ASCII, so all my scripts are both "basic 8859" and "utf-8" at the same
> time, and having Tcl 9 source them as utf-8 won't cause an issue.  But
> it sounds like Uwe directly entered the extended 8859 characters into
> the scripts.  Which very well may have made perfect sense if he had
> more than one or two of them per script.

Interesting thread.

Is there a way check a script file for such incompatibilities ahead of time?

Would this work as a solution?  You build your own Tcl/Tk and add or 
duplicate the source command from an earlier version that you are happy 
with.  Then you start up your app as you do currenly, and once it is 
loaded, you switch the source command to the new version and change the 
system encoding.