Neovim doesn't respect character encoding

[EmmasBox]

I used neovim to edit the SSH config on a system today and ended up running the SSH process into the ground because it apparently opens files encoded in IBM-1047 fine but decides to convert it to UTF-8 if they're not tagged. I was able to get around this by tagging it in IBM-1047 and writing to the file with the settings again, but it's a bit dangerous that it decides to auto-convert if files are not tagged.

[IgorTodorovskiIBM]

Hi, was the file untagged originally?

[IgorTodorovskiIBM]

I was able to reproduce. vim produces the desired behaviour, but neovim does not.

DEVUSER:/data/igor: >/bin/touch test.txt
DEVUSER:/data/igor: >chtag -tc 1047 test.txt
DEVUSER:/data/igor: >echo "HELLO WORLD" > test.txt
DEVUSER:/data/igor: >chtag -r test.txt 
DEVUSER:/data/igor: >ls -lT test.txt
- untagged    T=off -rw-r--r--  1 DEVUSER GROUP2 20 May 23 20:54 test.txt
DEVUSER:/data/igor: >nvim test.txt (edit the file)
DEVUSER:/data/igor: >/bin/cat test.txt
��<<|��|�<�/���/�ÎDEVUSER:/data/igor: >

@sachintu47 can you take a look when you get a chance?

[EmmasBox]

Hi, was the file untagged originally?

Yeah it was untagged and encoded in the IBM-1047 encoding.

[AnthonyGiorgio]

The real problem is the IBM sshd doesn't honor file tags. I've opened an internal defect that will hopefully address this one day.

[sachintu47]

@EmmasBox This is fixed. Could you please confirm by installing latest ?