diff options
| author | jan.nijtmans <nijtmans@users.sourceforge.net> | 2019-09-12 07:51:13 (GMT) |
|---|---|---|
| committer | jan.nijtmans <nijtmans@users.sourceforge.net> | 2019-09-12 07:51:13 (GMT) |
| commit | 1c7a85c59015cd02c24dd725b5b4e964f31ea263 (patch) | |
| tree | 3b4f7dc304e32c6e7a9de80d748b746fcbdecc19 /library | |
| parent | ea5368771d682a8a7023e718ad8635b193523866 (diff) | |
| parent | 400a5524e5f12e96c47dc1613835765f4a9f0271 (diff) | |
| download | tcl-1c7a85c59015cd02c24dd725b5b4e964f31ea263.zip tcl-1c7a85c59015cd02c24dd725b5b4e964f31ea263.tar.gz tcl-1c7a85c59015cd02c24dd725b5b4e964f31ea263.tar.bz2 | |
Fix Tcl part of [https://core.tcl-lang.org/tk/tktview?name=a179564826|a179564826]: Tk 8.6: prevent issues when encountering non-BMP Unicode characters.
This changes the handling of incoming 'invalid' 4-bute UTF-8 characters. They are no longer handled as 4 separate bytes, but as 2 Unicode characters.
(partial backported from 8.7). Still, Tcl will NEVER produce 4-byte UTF-8 byte sequences, so this can never hit Tcl applications/extensions by surprise.
More changes to Tk 8.6 expected improving this, but this Tcl change is a pre-requisite for that.
Diffstat (limited to 'library')
0 files changed, 0 insertions, 0 deletions