"Rion D'Luz" <[EMAIL PROTECTED]> writes: > I feel really stupid posting this but i'm at whits' end and searching the net > has turned up nada. > I'm running vim7.0 on ubuntu and AFAIK, it has unicode support.
Most distros these days enable UTF-8 locales by default. What does `locale` report? > Basically, my vimrc file as evolved over the years and i did something that > now results in my > seeing UTF-8 characters in the textfiles i'm editing; mostly as a result of > copy/paste from > webpages. > i.e. > Weeding for Your Library\u2019s Health > ^^^^^^^ That's actually a unicode character, (U+2019 RIGHT SINGLE QUOTATION MARK (’), specifically). Given its value, it's represented as a couple of bytes (0x80 0xE2) when encoded in utf-8. The file might be in utf-8, but vim is decoding that, and displaying them as single unicode characters to you … or maybe for some reason not believing that it can do so, and instead showing the substitute "\u2019" instead of the character? It's unlikely that it's a font-problem, since that usually manifests itself as a single block/unknown glyph … the font layout/renderer doesn't have the leeway to substitute the 6 character string "\u2019" when asked to draw a single unicode character. > I am not alone in the issue, but so far any solutions mentioned have come to > naught > and i'm not completely sure if the issue is vim or some stupid xterm setting. > But its a real PITA I'd believe it's a terminal problem. What terminal are you using? Does gnome-terminal (or konsole or whatever; something more modern than xterm) exhibit the same problem, or a different one (or none)? -- ...jsled http://asynchronous.org/ - a=jsled; b=asynchronous.org; echo [EMAIL PROTECTED]
pgpXzz4hC9smO.pgp
Description: PGP signature
