This is the "new" (second) bug report: UNICODE | >> Edit TC File commentghisler(Author) wrote: 2023-10-06, 07:10 UTC If possible, please report one bug per post if you want to see them fixed.
TC 11.02RC1 x86white wrote: 2023-09-12, 12:26 UTC * Execute cm_SetAttrib
* Select plugin attribute tc.comment and click the >> button
* Enter ✓ and press F2
* The value field now contains ? instead of ✓
If you press F2 or click on the button "F2 OK", the field "Value" is filled with approx. 230 characters instead of ✓.
TC 11.02RC1 x64
If you press F2 or click on the button "F2 OK", the field "Value" is filled with ?Ǣ (wrong character set) instead of ✓.
Please check.white wrote: 2023-10-05, 18:08 UTC If the file comment already contains ✓ and I use the >> button, the edit box shows 2 characters instead of ✓,
but these characters translate to a ✓ when I click OK.
Windows 11 Pro (x64) Version 22H2 (OS build Build 22621.2361) | TC 11.02RC1 x64/x86
See also fixed bug report: [TC 11.01] Change Attributes: Plugin value field doesn't seem to support unicode
HISTORY.TXT wrote:05.10.23 Release Total Commander 11.02 release candidate 1
13.09.23 Fixed: Change attributes: Field tc - comment didn't support setting Unicode comment (different codepage) (32/64)