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

Am 08.01.2025 um 11:58 schrieb Harald Oehlmann:

Am 08.01.2025 um 11:35 schrieb Uwe Schmitz:

Harald,
>

THanks, Uwe.
Sorry, for the inconvenience.
>
For me, this is a big step forward.
>
With tcl 8.6, I always have to type:
source -encoding utf-8 script.tcl
as I don't know the system encoding.
It is not setable for me.
So, this change is a big advantage, as now, I can type:
source script.tcl.
>

on all the systems I've worked on so far, I've been able to
to set the system encoding, even as a normal user.
Users of our in-house software stack (similar to BAWT, but only
for Linux) are advised to set iso8859-1 encoding, before running
any programs.
>
Anyhow, what we should have at least is a magic comment as described
in my other post. This would give you the option of placing
the encoding where it really belongs. And this would avoid
having to include the encoding with every source/tclsh call.
If you ever change the encoding, you have to find all this places
and correct them. Good luck to find them all...
>
To summarize, I am more and more getting to the opinion,
that Tcl9 forces developers to encode their source codes in utf-8.
Otherwise you end up in an encoding nightmare.
>
Best regards,
Uwe

 Sorry, I am MS-Windows only.
I can only set the system encoding system wide (well, the answer is more complicated - it depends on the application manifest and the system wide system encoding).
As I distribute my software worldwide, I am not in control of the system encoding.
 Sorry, different use-case, different answer.
 If you want this feature, please file a bug report at the bug tracker.
 Take care,
Harald
 

And you may change the behaviour in the automatically sourced startup file in your home folder or wherever, Linux folks may help.
rename source source2
proc source args {
source2 -encoding iso8859-1 {*}$args
}