On Wednesday, July 17, 2013 11:31:25 PM UTC+2, Ben Fritz wrote:
> On Wednesday, July 17, 2013 2:51:24 PM UTC-5, Zulox4 wrote:
> 
> > 
> 
> > I think that the problem is result of  "fileencoding" or "utf8 encoding" 
> > options.
> 
> > 
> 
> > I found another problem:
> 
> > 
> 
> > 1. I have 1 line in the buffer:
> 
> > s\x6fme\tt\x65xt\n\"Sa\155ba\u201d: \\\\net\\share
> 
> > 
> 
> > 2.After these commands 
> 
> > 
> 
> >    c}<C-R>="<C-R>""<CR>
> 
> > 
> 
> > the result in the buffer must change to ( on two lines):
> 
> > 
> 
> > some    text
> 
> > 
> 
> > "Samba”: \\net\share
> 
> > 
> 
> > But in my win32 vim version the char ” ( unicode \u201d ) after word Samba 
> > disappear.
> 
> > 
> 
> > When setting set encoding=utf8, the commands works as expected, also the 
> > "hanging indent" commands.
> 
> > 
> 
> > 
> 
> 
> 
> AHA! Now I know why I could not reproduce. I copy-pasted from my browser 
> instead of actually downloading the file. When I copy-paste, Vim happily 
> pasts the text, even if it cannot save it in the default Latin1 encoding. But 
> when I load a file with utf-8 characters as Latin1 encoding, the fancy quotes 
> in your input file show up as two characters instead of just one in Vim.
> 
> 
> 
> Thus, the line ending in "BL," becomes just long enough that Vim wraps it 
> when reformatting, since the line now has 2 extra characters.
> 
> 
> 
> > 
> 
> > Could have vim initialize in windows like in linux encoding to utf8 by 
> > default?
> 
> > 
> 
> 
> 
> Please see http://vim.wikia.com/wiki/Working_with_Unicode

I would like to initialize in vim (code), like the linux version, not with 
"vimrc" file config.
Thanks for helping !

-- 
-- 
You received this message from the "vim_dev" 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_dev" 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/groups/opt_out.


Raspunde prin e-mail lui