Loading ...
Sorry, an error occurred while loading the content.

52207Re: Gvim for Windows doesn't handle non-BMP characters when interchanging data with Windows OS

Expand Messages
  • JiaYanwei
    Oct 22, 2008
    • 0 Attachment
      Hello Tony,

      It's really to be the similar problem, but this one only arise under Windows
      operating system, the UTF-16le BOM problem is platform independence. I was 
      uncertain wherher a combined patch was convenient.

      On 2008-10-22 23:21:11, Tony Mechelynck wrote:
      > I expect this is related with the UTF-16le BOM problem you noticed this
      > past Saturday. Maybe a combined patch would be OK, since in both cases,
      > the problem involves using UCS-2 (where surrogates are undefined)
      > instead of UTF-16 (where surrogate pairs encode codepoints above the BMP)? 

      Best regards,
      You received this message from the "vim_dev" maillist.
      For more information, visit http://www.vim.org/maillist.php

    • Show all 7 messages in this topic