When build vim with MSVC, there is always a warning message like this
when compiling each source file:
x:\path\to\source\ascii.h : warning C4819: The file contains a character
that cannot be represented in the current code page (936). Save the
file in Unicode format to prevent data loss
The att
Hong Xu wrote:
> When build vim with MSVC, there is always a warning message like this
> when compiling each source file:
>
> x:\path\to\source\ascii.h : warning C4819: The file contains a character
> that cannot be represented in the current code page (936). Save the
> file in Unicode format to
>
> I can include this. However, the best solution is probably to make the
> compiler not give the warning message.
>
I don't think so. to say the least, it should not include DBCS characters.
I may accept it if it is writen in utf-8.
--
You received this message from the "vim_dev" maillist.
On 2011/8/21 23:53, Bram Moolenaar wrote:
When build vim with MSVC, there is always a warning message like this
when compiling each source file:
x:\path\to\source\ascii.h : warning C4819: The file contains a character
that cannot be represented in the current code page (936). Save the
file in Un
> I still think that the best solution is to remove all those characters,
> even encoded in any unicode, since many compilers cannot detect
> encoding. Removing these characters could improve the compatibility of
> the source code.
>
> Besides, for Microsoft's compiler, the only way for it to
Hong Xu wrote:
> On 2011/8/21 23:53, Bram Moolenaar wrote:
> >> When build vim with MSVC, there is always a warning message like this
> >> when compiling each source file:
> >>
> >> x:\path\to\source\ascii.h : warning C4819: The file contains a character
> >> that cannot be represented in the cur
