#2991 fconfigure -encoding now case sensitive

[Vince Darley]

cvs HEAD has a script-level incompatibility with older
versions of Tcl. Encoding names on all platforms are
now case-sensitive.

Previously the case-sensitivity depended on the
case-sensitivity of the underlying filesystem (i.e.
typically not case-sensitive on Windows and MacOS,
MacOS X).

At the very least the changelog should make this
incompatibility clear. Otherwise the behaviour should
be reverted to the old approach.

I have no real preference for either, but I do have at
least 1 piece of code which is affected (but easily fixed).

[Donal K. Fellows]

Logged In: YES
user_id=79902

The whole thing looks like pilot error to me, but I'm not an
encoding maintainer

[Don Porter]

Logged In: YES
user_id=80530

well, encoding names in scripts
have always had
to be in proper case to port
successfully to unix.

Most compatible thing we can do
is shift all values to lowercase
as they come in to make them
case insensitive everywhere
Will consider that after 8.5a2
release. Will be interesting to
see how much comment we get
on this matter.

[Vince Darley]

Logged In: YES
user_id=32170

I've no problem with the new behaviour, since it is more
consistent cross-platform. However, the ChangeLog should
document that this has changed (anywhere with a
case-insensitive filesystem, which can be Unix too -- e.g.
Darwin/MacOS X).

[Don Porter]

Logged In: YES
user_id=80530

Can you check the HEAD of Tcl and see
whether this is still an issue?

[Vince Darley]

Logged In: YES
user_id=32170

Indeed, CVS head now accepts things case-insensitively, at
least on WinXP.

[Don Porter]

Logged In: YES
user_id=80530

ok, I think we're back to the
status quo ante then
(case sensitive on unix,
insensitive on Windows)

Feel free to re-open if needed.
Closing now.