On Sat, Aug 2, 2014 at 8:12 PM, Tony Mechelynck <[email protected]> wrote: > On 31/07/14 20:50, Paul Moore wrote: >> >> On 31 July 2014 19:38, Bram Moolenaar <[email protected]> wrote: >>> >>> Paul Moore wrote: >>> >>>> On Windows, Vim does not correctly display international characters. >>>> To demonstrate this, create a file in UTF-8 encoding with the Unicode >>>> characters \x5000 \x5001 \x5002 in it. These should display as Chinese >>>> chacaters. >>> >>> >>> The question is: What version of Windows? Reading the comments it >>> appears the behavior changed at some point. >> >> >> Sorry, this is Windows 7 64-bit. >> >>> From my personal experience, I don't think the behaviour has changed, >> >> I was just used to Vim not ever displaying "unusual" characters >> properly, but I saw them so infrequently that it didn't bother me and >> I never dug into the exact details. But I recently encountered a file >> with UTF8 test data in it that was difficult to follow because of the >> rendering issue. It was a one-off problem, but annoying enough that I >> looked at other editors (I couldn't convince myself that it was *just* >> a rendering issue and I wasn't at risk of corrupting the data). I was >> surprised to find that *every* other editor displayed the file >> flawlessly. >> >>> There are plenty of Chinese Vim users, I'm sure they would have >>> complained loudly if Chinese characters don't show up. >> >> >> If I understand the issue it is with display of characters which don't >> have a glyph defined in the current font. Windows appears to have a >> way of falling back to another font which does contain the glyphs if >> needed, but the flag I disabled stops that fallback happening - hence >> the bad display. >> >> I guess Chinese users won't see an issue as I presume their fonts will >> contain the necessary glyphs. >> >> Paul >> > > From what I read in the help, the only version of Vim which will try to use > a glyph from a different font if the font you specified doesn't have the > required glyph, is gvim with GTK2 GUI, which happens to be a Linux version > (and maybe a rarely-used Mac+X11 version).
I believe MacVim (indirectly?) also searches all fonts if the current font is missing a needed glyph. And that is the purported origin of this performance issue: https://code.google.com/p/vim/issues/detail?id=210 (I realize now that I probably reported that bug to the wrong bug tracker.) Justin M. Keyes -- -- 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/d/optout.
