Find Files may search a text line in different encodings at once, for example, in ANSI and Unicode, which is quite useful if we don't know it for sure. However, when we look at the result in Lister using its View function, it may show or not the text depending on its own encoding. As a result, if Find Files found a text, for example, in Unicode UTF-16, but Lister uses ANSI-like encoding (Text only or Binary for non-text files), it will show nothing (Not found). Need to manually switch encoding in Options menu, which may be not very obvious and easy to choose.
Suggestion: add the internal "encoding" parameter to any file in Find Files results (at least for first found occurrence, if there are multiple in different encodings in one file) and send it to Lister for View (F3) operation from FF dialog. Lister should accept this encoding and show text as it was found, without setting encoding by its own logic.
Find Files: keep an encoding of found text for Lister
Moderators: white, Hacker, petermad, Stefan2
Find Files: keep an encoding of found text for Lister
Desktop: Windows 11 Pro 23H2, TC 11.03(RC). Mobile: Pixel 5a, Android 14, TC 3.42b5
Re: Find Files: keep an encoding of found text for Lister
Support++++ if it is feasible
License #524 (1994)
Danish Total Commander Translator
TC 11.03 32+64bit on Win XP 32bit & Win 7, 8.1 & 10 (22H2) 64bit, 'Everything' 1.5.0.1371a
TC 3.50 on Android 6 & 13
Try: TC Extended Menus | TC Languagebar | TC Dark Help | PHSM-Calendar
Danish Total Commander Translator
TC 11.03 32+64bit on Win XP 32bit & Win 7, 8.1 & 10 (22H2) 64bit, 'Everything' 1.5.0.1371a
TC 3.50 on Android 6 & 13
Try: TC Extended Menus | TC Languagebar | TC Dark Help | PHSM-Calendar
Re: Find Files: keep an encoding of found text for Lister
I'd like this improvement, too. It doesn't happen often, but when it does, it surprises me at first and then I have to try different encodings to find the correct one.
Windows 7 Pro x64, Windows 10 Pro x64