You can export windows registry files in plain text as well. Explore the "save as" options.
-- Quoting Christian Brabandt ([email protected]): Subject: Re: Windows Registry Editor text files (.REG) in Unicode (?)?encoding - displayed as garbage Date: Wed, Dec 02, 2009 at 10:25:19PM +0100 Hi Frantisek! On Mi, 02 Dez 2009, Frantisek Rysanek wrote: > following up on my Unix-originated habit, I'm using Vim as my > favourite text editor for anything that resembles plain text in > Windows. The Windows context menu item "edit with Vim" is very useful > indeed :-) > > And that's where I have a problem with .REG files. > If the file is encoded as plain ASCII, that's no problem. > The problem is that Regedit in XP exports Unicode (or what), maybe > utf-16 (or some other multibyte charset). If I try "edit with Vim" on > such files, I get a screenful of garbage. > > I'm using the basic Windows build of Vim (gvim.exe) that gets > installed by the "allaround Windows installer" of VIM 7.2, available > at www.vim.org. > > Is there an easy way out? A few dark curses in the command line? > ":help multibyte" was not much help... I don't even know what > encoding i should try. > Or is the default Windows build missing some important compile-time > features? Some parts of "multibyte" support? > :version only mentions +multi_byte_ime/dyn , not +multi_byte. > > Any ideas are welcome :-) I believe Windows uses a UTF-16 encoding, so try reloading the file with :e! ++enc=utf-16le (Or whatever the windows encoding is) regards, Christian -- :wq! -- You received this message from the "vim_use" maillist. For more information, visit http://www.vim.org/maillist.php -- You received this message from the "vim_use" maillist. For more information, visit http://www.vim.org/maillist.php
