Re: [TCLCORE] Unicode in Tcl 9 - a commentary and critique

[Jan N. <jan...@gm...>]

Op do 2 feb. 2023 om 23:09 schreef Jan Nijtmans:

> Thanks.  I'll have a look.
>

Well, I know the testcases are still not handled, that's OK. But
two things I can already report (which you - most likely -
didn't notice yet).

First, an example in Tcl 8.7:
    $ tclsh8.7 (core-8-branch)
    % fconfigure stdin
-blocking 1 -buffering line -buffersize 4096 -encoding utf-8 -eofchar {}
-nocomplainencoding 1 -strictencoding 0 -translation auto -closemode
default -inputmode normal -mode 38400,n,8,1 -xchar { }
Note the "-nocomplainencoding 1 -strictencoding 0". This should correspond
with "-endingprofile tcl8"
    $ tclsh8.7 (apn-encoding-profile)
    % fconfigure stdin
-blocking 1 -buffering line -buffersize 4096 -encoding utf-8
-encodingprofile {} -eofchar {} -translation auto -closemode default
-inputmode normal -mode 38400,n,8,1 -xchar { }
    %
I see "-encodingprofile {}". That's not what I would expect. Then, another
issue:
    % fconfigure stdin -e
    {}
    % fconfigure stdin -en
    utf-8
    % fconfigure stdin -encoding
    utf-8
    % fconfigure stdin -encodingp
    {}

So, specifying "-e" or "-encodingp" selects "-encodingprofile", but when
the string has
length 2 up to 9 it selects "encoding". My suggestion: just use "-profile"

That's it for now.

Regards,
       Jan Nijtmans