Re: Tcl9: source files are interpreted as utf-8 by default

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.