Hello Yakov, I've encountered similar problems. Example: I've exported unicode file from registry editor, and then tried to open it in vim: $ gvim ddd.reg
Vim shows file as follows: [EMAIL PROTECTED]@[EMAIL PROTECTED] etc (first string of file is "Windows Registry Editor Version 5.00"). Then I write in vim: :set enconding encoding=cp1251 :set encoding=utf8 And nothing changes!. There are sill ^@'s in file. I'm forced to reload file using :e And then it works as needed - readable text is shown. So - my question reated to previous message of Hugh Sasse is - How can we apply new encoding to current window (buffer, etc.) without reloading file? Thanks in advance! Tuesday, April 11, 2006, 1:07:27 PM, you wrote: >> Date: Fri, 7 Apr 2006 12:08:23 +0100 (WEST) >> From: Hugh Sasse <[EMAIL PROTECTED]> >> To: Vim Help list <[email protected]> >> Subject: editing WinXP text files - multibyte? >> >> If, on WinXP, I do >> >> regedit /e regfile.reg >> >> I get a file with the contents of the registry. However, in my Gvim >> (6.4) I see nulls for every other character (^@), which agrees with >> remarks about ucs-2le in the docs. This is particularly >> unpleasant to read and edit. Notepad will display it to read, but >> for editing I'd rather use gvim. Both >> :he utf-16 | he ucs2-le >> turn up nothing, and the utf-8 things don't seem relevant. :he >> encoding tells me I can't use that to edit a file that has loaded >> incorrectly, so I'll have to re-open the file. But that means >> right-clicking the file to access vim won't work. YL> I think you need to set option 'fileencodings' properly in YL> your vimrc (:he 'fileencodings'). The option 'bomb' YL> (:he 'bomb') might be relevant, too. I am not specialist in YL> encodings, though. YL> Yakov -- Best regards, Mikalai Chaly mailto:[EMAIL PROTECTED]
