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

Folks,
thanks for all your suggestions and discussions.
I think this discussion has helped to bring the topic
into focus. May be that other Tcl users will be affected
by this incompatibility when migrating to Tcl9.
We have now examined the problem from many different
angles and have come up with more or less elaborate solutions.
My conclusion is: If migrating to Tcl9 all your source files
have to be encoded in utf-8. Otherwise you will have much more
maintaining efforts (adding iso8859, redefine commands, roll your own tcl, ...).
This can be mitigated if we introduce one of the changes I have proposed:
1. a switch (environment variable?) that restores the Tcl8 behavior and/or
2. a magic comment within the source file that can be used to determine the encoding.
I try to file a ticket about this.
Nevertheless, this point should be noted under "Important Incompatibilities in Tcl 9.0"
on the Tcl9 page:
https://www.tcl.tk/software/tcltk/9.0.html
Thanks again for your time!
Happy Tcl'ing
Uwe
Am 09.01.2025 um 05:15 schrieb Luc:

On Thu, 9 Jan 2025 03:57:14 -0000 (UTC), Rich wrote:
 

Display depends upon whether your font being used had a glyph for the
codepoint - no glyph in the font, no display in the text widget

 

That also depends upon what your system encoding was set to, and
>
That is probably when support for the extended Unicode characters
(planes beyond the BMP) started to be added.
>

**************************
 Nothing to do with fonts or encoding. The problem vanished as soon as
I used 8.6.13, later 8.6.15. It was extended Unicode characters.
 You can see my discussion here, at the end of the page:
 https://wiki.tcl-lang.org/page/Unicode