Yes, but it doesn't in my end, unfortunately. I am grateful for all your help, but so far it hasn't changed anything.
I have absolutely no idea of what's going on here. I have submitted a support case - do you want me to continue in this thread or to work with Support to resolve the issue?
I rename the file every time, before I open it, to a new unique name so as to not trigger SlickEdit's built-in memory of file encodings. I have tried both with and without customized settings, even a clean install. Nothing works. And it hasn't for years, which is why I have been looking for another option recently because it is getting to be really annoying that I can't get SlickEdit to work for me.
Obviously, I'd prefer to get SlickEdit to work but I am ready to switch to another editor, if this issue cannot be resolved. I work almost full-time in UTF-8 encoded PHP files containing Danish national characters so this is a major hassle for me. Especially because the UTF-8 BOM breaks some web clients and makes the the XHTML/1.0 validator fail (the whole point of XHTML/1.0 Strict is that it can be validated sensibly).
Also, when you switch a lot between ASCII and UTF-8 files, it is a tedious hassle to have to use File>Save As to determine the encoding. This should be shown prominently on the status line or in the buffer list (I use the BRIEF emulation). I have suggested this to support long ago but nothing has happened.
Graeme reported this:
"If I turn on "line hex" in the view menu I get the incorrect version that you're getting."
So there must be some issue somewhere in there, which I am running into all the time.
A final note: I never use SlickEdit workspaces, I always open and close my files on the fly from a console window.