From: <no...@tc...> - 2025-10-08 08:18:54
|
Automated mail by fx, on behalf of no...@tc... Ticket Change [be56fc140d27d5ba45d6ce25015e9935ae0fa479b61ec099927efaac4fda07c0] ["crc32 -filename $name" end in error on files with special content (not encoding problem)] By oehhar For Tcllib On 2025-10-08T08:03:21.101 Details https://core.tcl-lang.org/tcllib/tinfo?name=be56fc140d27d5ba45d6ce25015e9935ae0fa479b61ec099927efaac4fda07c0 Ticket https://core.tcl-lang.org/tcllib/tktview/7bd2d439ca61da14a9fc5e8372e5fb1f86c28ff1 Changed Fields icomment: I have tested this with tcllib 2.0 and tcl 2.0 release and tcl 8.6.13 and tcl 9.0.2. Both give the same result without error: <verbatim> % lappend auto_path {C:\ est\ cllib20\ cllib2.0} //zipfs:/lib/tcl/tcl_library //zipfs:/lib/tcl C:/myprograms/tcl9.0_x64/lib //zipfs:/lib/tk/tk_library //zipfs:/lib/tk/tk_library/ttk {C:\ est\ cllib20\ cllib2.0} % package require crc32 1.3.4 % set p {C:\ est\ cllib20\ cllib2.0\\valtype\\luhn5.tcl} C:\ est\ cllib20\ cllib2.0\\valtype\\luhn5.tcl % ::crc::crc32 -filename $p 2493131738 </verbatim> By source code inspection, the relevant line is there: <verbatim> fconfigure $opts(-channel) -translation binary </verbatim> This implies the binary (8859-1) encoding. Sorry, I dont see any issue. Take care, Harald login: oehhar priority: 3 Low resolution: Works For Me severity: Minor username: oehhar ------------------------------------------------------------ See Tcl/Tk development @ http://core.tcl-lang.org/ ------------------------------------------------------------ |