Path: ...!eternal-september.org!feeder3.eternal-september.org!news.eternal-september.org!eternal-september.org!.POSTED!not-for-mail
From: Harald Oehlmann <wortkarg3@yahoo.com>
Newsgroups: comp.lang.tcl
Subject: Re: Tcl9: source files are interpreted as utf-8 by default
Date: Wed, 8 Jan 2025 11:58:08 +0100
Organization: A noiseless patient Spider
Lines: 49
Message-ID: <vlllo0$2llov$1@dont-email.me>
References: <vjhiar$3f9go$1@dont-email.me> <vljmj2$29vdo$1@dont-email.me>
 <vljno8$24ig0$1@dont-email.me> <vllkcu$2nvqo$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 11:58:08 +0100 (CET)
Injection-Info: dont-email.me; posting-host="2478bf1b0e4e52711e6a09f7e3b46e96";
	logging-data="2807583"; mail-complaints-to="abuse@eternal-september.org";	posting-account="U2FsdGVkX1/zkPUOEtqZnv0mGwk9CZ0Y"
User-Agent: Mozilla Thunderbird
Cancel-Lock: sha1:Yo/OUb4EXxHzXUY12dY8M05Rcdc=
Content-Language: en-GB
In-Reply-To: <vllkcu$2nvqo$1@dont-email.me>
Bytes: 2810

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