So, selected and slightly edited quotes from this post:
In other words, for some htm files insde "HTML text (Strip tags)" view Lister will change encoding from UTF-8 to ANSI by pressing "5" key, then again to UTF-8 via next "5" keypress and so on - this is right behaviour IMHO. And for some files "5" keypress won't change encoding inside "HTML text (Strip tags)" view - I see it as wrong behaviour. Both files in example are UTF-8, so switching to UTF-8 rendering should be possible for both, and it is supported for both if we'll use F3+5+7 instead of F3+5+5 in reproduce steps.post wrote:test without plugins intalled (default wincmd.ini settings):
1) sample file (inside archive) http://rghost.ru/66zvmdCsC:
* F3 shows file with "HTML text (Strip tags)" and "UTF-8" checked.
* F3+5+5: "HTML text (Strip tags)" and "UTF-8" checked.
2) another file (inside archive; download password: utf8htm2): http://rghost.ru/7qs27Nyq6
* F3: just "HTML text (Strip tags)" checked.
* F3+5+5: still just "HTML text (Strip tags)" checked.
The only notable difference between both HTM files I can see is that second one has a BOM in UTF-8 (at least Akelpad can detect it there). If behaviour for both files is by design and switching to ANSI for htm files inside "HTML text (Strip tags)" view intentionally allowed only for files with byte order mark, it must be documented, since it is not expected: Lister allows to switch bitween ANSI and UTF-8 for UTF-8 *.txt files with and without BOM.
edit: fixed note about BOM because akelpad shows "*BOM" status for files without BOM.