[TC 11.01] Change Attributes: Plugin value field doesn't seem to support unicode

[white]

If you use cm_SetAttrib to set the file comment to ✓, it will set the comment to ? instead.

Discussed in the English forum here:

Did some more experimenting, trying to use '✓' with your method and somehow it doesn't stick, i get '?' instead when reopening 'files/change attributes menu trying to save the preset.

Either a bug or not supported. Note that in the Change attributes dialog, if you change plugin field tc.comment and use the >> button to enter ✓, it also places ? in the value field.

[ghisler(Author)]

Please provide an example of the parameters you used.

[tuska]

Please provide an example of the parameters you used.

Here and here are examples.

[white]

Example without parameters:

* Execute cm_SetAttrib
* Set plugin attribute tc.comment to ✓ and click OK
* ? is saved instead of ✓ and if you reopen cm_SetAttrib then it also shows ? instead of ✓

And:

* Execute cm_SetAttrib
* Select plugin attribute tc.comment and click the >> button
* Enter ✓ and press F2
* The value field now contains ? instead of ✓

[ghisler(Author)]

You are right, it doesn't currently support Unicode. Use Ctrl+Z instead. I will investigate the problem.

[tuska]

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)

This is partly fixed.
Thanks!

Comment: ✓

1. OK: Button with e.g. command: OPENATTRIBUTES=Comment-OKii_for_FilesFolders (F2 saved setting)
2. OK: Files > Change Attributes... > Change plugin attributes: > tc | comment | ✓ > OK

---

* Execute cm_SetAttrib
* Select plugin attribute tc.comment and click the >> button
* Enter ✓ and press F2
* The value field now contains ? instead of ✓

TC 11.02RC1 x86
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 ?Ǣ instead of ✓.

[white]

This is partly fixed.

Confirmed. When using the >> button, I still get ? instead of ✓.

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.

[ghisler(Author)]

Sorry, I didn't notice that there were two bug reports in one post.
If possible, please report one bug per post if you want to see them fixed.

[tuska]

If possible, please report one bug per post if you want to see them fixed.

Separate bug report:
[TC 11.02] Change Attributes: Plugin value field doesn't support unicode | >> Edit TC File comment

Due to the separate bug report, I consider this issue to be fixed.
Thank you for your efforts!

[ghisler(Author)]

Moderator message

Moved to fixed bugs