if has("multi_byte")
if &termencoding == ""
let &termencoding = &encoding
endif
set encoding=utf-8
setglobal fileencoding=utf-8
"setglobal bomb
set fileencodings=ucs-bom,utf-8,latin1
endif
--
--
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 vim_use+u...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
That's a tad too apologetic for my taste. I have never been able to work
with Indic scripts in Vim. You might get a base character to be
displayed correctly, but things get mangled quickly once you add the
diacritic vowels and ligatures to the mix. What's worse, the cursor
tends to jump around unpredictably when editing Indic text.
But maybe your setup works better.
No, my setup doesn't work any better, actually. I have no knowledge of anything but U.S. English and the little bit of Latin and Japanese I remember from high school and college respectively. But the OP says he sees nothing but empty boxes, i.e. the "no character" glyph. I'm pointing out that THAT particular problem is because the font being used simply does not have a representation for those characters. THAT part of the problem is not Vim's fault.
I gather that even if the OP finds a good Indic font (sorry if that is misusing the term), Vim won't present it very well. But at the very least the blank "no character" boxes should go away.
Vim shouldn't have trouble displaying the emoticons anyway, if you can find a monospace font for them. They might be a little difficult to make out, if your font size is too small, but they should be displayed at least.