On Saturday, September 9, 2017 at 12:16:27 PM UTC-6, Tony Mechelynck wrote: > In your Windows gvim, at the point where you would be reading your > problematic file, do instead > > :verbose set enc? > > If the answer is anything other than utf-8, then you cannot display > the file in gvim because the UTF-16le of the file cannot be translated > into whatever it is that gvim is using to represent characters in > memory. > > See http://vim.wikia.com/wiki/Working_with_Unicode
Hi Tony, Executing ":verbose set enc?" showed latin1. After reading the doc to be honest my minimal understanding of the topic was grayed even more. The sections of the manual around "*45.4* Editing files with a different encoding" helped however I am still unclear. After setting an appropriate Unicode font in my vimrc (set guifont=courier_new:h11) and opening the file with ":e ++enc=utf-16le utf16.txt", the file was loaded with conversion errors (all upside down question marks). Executing ":set encoding=utf-16le" and reloading yet again with ":e ++enc=utf-16le utf16.txt" worked, I can now view the file? Why didn't opening the file with "++enc=utf-16le" accomplish all that ":set encoding=utf-16le" did? Thanks a lot for the help. -- -- You received this message from the "vim_use" maillist. Do not top-post! Type your reply below the text you are replying to. For more information, visit http://www.vim.org/maillist.php --- You received this message because you are subscribed to the Google Groups "vim_use" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
